Skip to content

Create Repo / Org make --forge-type optional#416

Merged
gabriel-samfira merged 1 commit into
cloudbase:mainfrom
ChristopherHX:optional-forge-type-for-gitea
May 29, 2025
Merged

Create Repo / Org make --forge-type optional#416
gabriel-samfira merged 1 commit into
cloudbase:mainfrom
ChristopherHX:optional-forge-type-for-gitea

Conversation

@ChristopherHX

Copy link
Copy Markdown
Contributor
  • This makes gitea garm usage unnessary complex

@ChristopherHX ChristopherHX force-pushed the optional-forge-type-for-gitea branch from 59892a5 to 8f85747 Compare May 29, 2025 11:23
Comment thread cmd/garm-cli/cmd/common.go Outdated
@ChristopherHX ChristopherHX force-pushed the optional-forge-type-for-gitea branch 2 times, most recently from 09199bc to 897bacc Compare May 29, 2025 16:13
@ChristopherHX ChristopherHX changed the title Proposal: Create Repo / Org make --forge-type optional Create Repo / Org make --forge-type optional May 29, 2025
@ChristopherHX ChristopherHX marked this pull request as ready for review May 29, 2025 16:17

@gabriel-samfira gabriel-samfira left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As I wanted to submit a comment, you pushed a commit that solved that comment and GH erred out because of the outdated commit I was commenting on 😄 .

This LGTM. If tests pass, we can merge.

@gabriel-samfira

gabriel-samfira commented May 29, 2025

Copy link
Copy Markdown
Member

To fix the lint error, you can probably run:

golangci-lint run --build-tags=testing --fix

run:

make install-lint-deps

to get the needed binaries.

To run the tests locally, you can run:

make test

* This makes gitea garm usage unnessary complex

Signed-off-by: Christopher Homberger <christopher.homberger@web.de>
@ChristopherHX ChristopherHX force-pushed the optional-forge-type-for-gitea branch from 897bacc to efd725e Compare May 29, 2025 16:37
@ChristopherHX

ChristopherHX commented May 29, 2025

Copy link
Copy Markdown
Contributor Author

To run the tests locally, you can run:

make test

Not so easy, on my system.

It's much easier for me once the CI does no longer need approval, maybe for the second PR.

Linter complained about unused functions as well, maybe your version is an older v1. v2 is not compatible at all

@ChristopherHX

ChristopherHX commented May 29, 2025

Copy link
Copy Markdown
Contributor Author

This passed locally

go test ./... -tags testing

make test
more like, due to linuxism

/bin/bash: line 0: cd: /var/folders/yt/nn49l1_57rb2bbtj13r8yc040000gn/T/tmp.mFOQBSGnO5/garm: No such file or directory

I force pushed only, because you do not seem to use my preferred squash merging strategy

@gabriel-samfira

Copy link
Copy Markdown
Member

more like, due to linuxism

probably due to the shell used. Changing:

garm/Makefile

Line 70 in 18ef27b

@cp -R ${ROOTDIR} ${TMPDIR}

to

@cp -R ${ROOTDIR} ${TMPDIR}/.

will make it work on your system as well.

@gabriel-samfira gabriel-samfira merged commit c19bf2f into cloudbase:main May 29, 2025
5 of 6 checks passed
@gabriel-samfira

Copy link
Copy Markdown
Member

Thanks!

@ChristopherHX

Copy link
Copy Markdown
Contributor Author

probably due to the shell used. Changing:

Actually not, this was for example macOS and the error is of a different kind.

For lxd, I remote patched garm on my ubuntu arm64 server. I am testing with the k8s provider to not have to use my old windows/linux laptop with weak battery or doing remote development.

@gabriel-samfira

Copy link
Copy Markdown
Member

Actually not, this was for example macOS and the error is of a different kind.

if you have a bit of RAM to spare, you could probably use multipass on Mac to get a quick ubuntu VM up and running locally.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants