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.
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.
telackey
changed title from 49: Use a Personal Access Token to access private modulees. to 49: Use a Personal Access Token to access private modules.2023-07-06 19:55:25 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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 useGITHUB_TOKEN--and cause confusion since this is not the same token.Something like
GIT_VDB_TO_TOKENmight do, since we could follow theHOST_NAME_TOKENpattern for other repos if needed.49: Use a Personal Access Token to access private modulees.to 49: Use a Personal Access Token to access private modules.LGTM, much simpler