-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Dev process] Complete the switch to GitHub Actions #4834
Comments
@Jermolene Would you be able to address the remaining task in the issue description? I don't have write/admin access, which is required for the task: Configure the necessary GitHub token in this repo's settings and test the I believe I'm not sure of the urgency of keeping |
Hi @ento given that Travis CI is switched off, I didn't bother with creating a test branch. I created an access token with "public_repo" access, and saved it as the secret "GITHUB_PUSH_TOKEN"; it remains to be seen whether that's sufficient. |
Now I'm going to push a commit with a minor change for testing. |
Hi @ento the test build failed while executing |
The token doesn't appear to be passed to the I expect there to be a Could you double-check that the secret is configured in the repo? https://github.com/Jermolene/TiddlyWiki5/settings/secrets Given the log output that we do see, I guess
Subsequent outputs are supressed due to the I just checked locally that |
Hi @ento I didn't notice at first, but it's failing to add the new token with the message "Failed to add secret. Name is invalid". |
Maybe any name prefixed with |
Hi @rmunn the prefix We can't use But perhaps it would be good to use |
I've updated ci.yml to use |
Thank you @ento things seem to be working (I haven't tested pushing to tiddlywiki-com yet, but pushing master works). Is there any other cleanup needed besides closing down Travis? |
Thank you for sorting the secrets situation out! I think that's all as far as cleanups go: disable this repo on Travis's side and confirm pushing to tiddlywiki-com works. I'll go ahead and optimistically close this issue, assuming tiddlywiki-com will probably work, but please feel free to re-open to track the Travis part or anything else. If anything goes wrong on the tiddlywiki-com branch, it can be tracked with a new issue (or this issue could be re-opened / whatever works) - and do let me know. |
Hi @ento we may have a minor issue with merging to "tiddlywiki-com". I merged #4842 but it didn't trigger a build at https://github.com/Jermolene/TiddlyWiki5/actions. I note that the tests were run when the PR was opened (https://github.com/Jermolene/TiddlyWiki5/actions/runs/243322046). |
Hi @ento apologies, I've just realised that the reason that the actions didn't run when I pushed to |
Good to hear you were able to solve the issue :) |
Follow-up to #4793
build-prerelease
andbuild-tiddlywiki-com
jobs and test themon.push.branches
and adjust theif
conditions of jobs so that they get run on that branch. (This needs to be done in a branch in this repo, not a fork, so that the workflow can access the secret configured in the next step.)GITHUB_PUSH_TOKEN
that has push access toJermolene/jermolene.github.io
build-*
jobs work. i.e. the workflow gets run, the result is green, andjermolene.github.io
gets updatedci.yml
, merge the branch. Don't forget to undo the changes made toon.push.branches
andif
conditions.Done by #4836:
.travis.yml
bin/ci-*
scripts andci.yml
that mention TravisThe text was updated successfully, but these errors were encountered: