Commit Graph

14 Commits

Author SHA1 Message Date
f4db8e722f Use ';' for the rm.
Some checks failed
Test / Run unit tests (pull_request) Failing after 50s
Test / Run integration tests (pull_request) Failing after 2m47s
2023-07-10 14:26:02 -05:00
7cca02d66f Use other plugeth branch.
Some checks failed
Test / Run unit tests (pull_request) Failing after 1m1s
Test / Run integration tests (pull_request) Failing after 2m55s
2023-07-10 14:24:39 -05:00
5a2a8765b7 Restore earlier (working) form of the git config command.
Some checks failed
Test / Run unit tests (pull_request) Failing after 49s
Test / Run integration tests (pull_request) Failing after 2m38s
2023-07-10 14:13:01 -05:00
d921095d80 Missing ':'
Some checks failed
Test / Run unit tests (pull_request) Failing after 47s
Test / Run integration tests (pull_request) Failing after 28s
2023-07-10 14:01:58 -05:00
e5eb13a27e Try workaround for proxy issue.
Some checks failed
Test / Run unit tests (pull_request) Failing after 54s
Test / Run integration tests (pull_request) Failing after 31s
2023-07-10 13:56:37 -05:00
94ec8c2436 Try workaround for proxy issue.
Some checks failed
Test / Run unit tests (pull_request) Failing after 55s
Test / Run integration tests (pull_request) Failing after 3m21s
2023-07-10 13:50:06 -05:00
fec6393913 Try workaround for proxy issue.
Some checks failed
Test / Run unit tests (pull_request) Failing after 47s
Test / Run integration tests (pull_request) Failing after 2m19s
2023-07-10 13:45:48 -05:00
2af53524bf Take certain steps regardless.
Some checks failed
Test / Run unit tests (pull_request) Failing after 44s
Test / Run integration tests (pull_request) Failing after 27s
2023-07-10 13:34:50 -05:00
0926306330 rename token 2023-07-07 13:09:18 +08:00
2bd312f0d0 49: Use a Personal Access Token to access private modules. (#4)
Some checks failed
Test / Run unit tests (pull_request) Failing after 49s
Test / Run integration tests (pull_request) Failing after 20s
I left it unchanged in the PR, but I would recommend a variable name other than `GITEA_TOKEN`, as I suspect that will be used by Gitea at some future date--like Github use `GITHUB_TOKEN`--and cause confusion since this is not the same token.

Something like `GIT_VDB_TO_TOKEN` might do, since we could follow the `HOST_NAME_TOKEN` pattern for other repos if needed.

Co-authored-by: Thomas E Lackey <telackey@bozemanpass.com>
Reviewed-on: #4
Co-authored-by: Thomas E Lackey <telackey@noreply.git.vdb.to>
Co-committed-by: Thomas E Lackey <telackey@noreply.git.vdb.to>
2023-07-07 04:36:30 +00:00
9b47315024 use access token for gitea 2023-07-07 01:45:43 +08:00
95797252ed dockerfile cleanup 2023-07-03 12:58:41 +08:00
5e8f283897 [dev] docker go build 2023-07-03 12:58:41 +08:00
ccb517bf61 dockerfile, .gitignore 2023-06-23 21:21:14 +08:00