Bug - scheduled test #254
Comments
|
the fix probably should be in ESET-KeyGen/.github/workflows/test.yml |
|
i figured it out, that the secret token is used to push timestamp change in the readme file in my forked repo. |
|
maybe the test should run on a separate branch not on main, so that when forked the test does not run automatically, or else too many tests will run. by default when forking, "Copy the master branch only" is checked. i didn't test this suggestion, i don't know if this is possible, it's just a wild guess |
|
You can remove test.yml from the repository after a fork. |
|
yes, i actually modified the cron job time so that it doesn't run anymore, while still avoiding conflicts during repo sync if the test is updated. previously my mailbox was spammed daily with test failures from the fork. the permanent fix would be to have the test file and run it on a separate testing branch, rather than on master. |
during scheduled test, throws error during push.
Push changes to repo 0s
Run ad-m/github-push-action@master
with:
branch: refs/heads/main
github_url: https://github.com
push_to_submodules: on-demand
directory: .
/home/runner/work/_actions/ad-m/github-push-action/master/start.sh: line 18: Missing input 'github_token: ${{ secrets.GITHUB_TOKEN }}'.: bad substitution
Push to branch refs/heads/main
Error: Invalid exit code: 1
at ChildProcess. (/home/runner/work/_actions/ad-m/github-push-action/master/start.js:30:21)
at ChildProcess.emit (node:events:519:28)
at maybeClose (node:internal/child_process:1105:16)
at ChildProcess._handle.onexit (node:internal/child_process:305:5) {
code: 1
}
May I ask what exactly pushes and where? Why is this step needed. Using the github token on a scheduled background activity without me knowing, looked very fishy. I am sure it's not, but can we have a detailed explanation of what's going on here? thank you
The text was updated successfully, but these errors were encountered: