Open bastelfreak opened 2 years ago
Hi @bastelfreak, This action should run on a schedule
event or a workflow_dispatch
event.
Example:
# Controls when the action will run.
on:
# can be used to run workflow manually
workflow_dispatch:
schedule:
# Automatically run on every Sunday
- cron: '0 0 * * 0'
Does the token for actions/checkout@v2 actually needs the workflow scope?
I think the action should work without this.
The action is marked as successful, even when the push failed. I think that should be changed?
I need to update this behavior.
Does the token for actions/checkout@v2 actually needs the workflow scope?
I think the action should work without this.
If I add it to a repo without this, it fails to push a branch saying that the workflow permission is not there, however after I add it, run the workflow, then it succeeds, then I remove it from the workflow, run it again and it still works. Looks like a bug of some kind. I am not sure what is going on there.
If I add it to a repo without this, it fails to push a branch saying that the workflow permission is not there, however after I add it, run the workflow, then it succeeds, then I remove it from the workflow, run it again and it still works. Looks like a bug of some kind. I am not sure what is going on there.
Hi @desecho, Thanks for the bug report. :+1: I have not worked on this for sometime. I will check it out and try to reproduce it when I get some time.
Does the token for actions/checkout@v2 actually needs the workflow scope?
It seems that it does need a workflow-scoped token. Otherwise, I get an error when the version updater action tries to push a new branch. Not sure why is that but I found the solution here: https://github.com/orgs/community/discussions/27072
The action is marked as successful, even when the push failed. I think that should be changed?
I need to update this behavior.
Fixed in https://github.com/saadmk11/github-actions-version-updater/pull/17/
Does the token for actions/checkout@v2 actually needs the workflow scope?
It seems that it does need a workflow-scoped token. Otherwise, I get an error when the version updater action tries to push a new branch. Not sure why is that but I found the solution here: https://github.com/orgs/community/discussions/27072
GitHub Actions Log when PAT without workflow
scope is used:
! [remote rejected] gh-actions-update-1665821908 -> gh-actions-update-1665821908 (refusing to allow a Personal Access Token to create or update workflow `.github/workflows/new.yaml` without `workflow` scope)
Does the token for actions/checkout@v2 actually needs the workflow scope?
I think the action should work without this.
If I add it to a repo without this, it fails to push a branch saying that the workflow permission is not there, however after I add it, run the workflow, then it succeeds, then I remove it from the workflow, run it again and it still works. Looks like a bug of some kind. I am not sure what is going on there.
I can confirm this. Not sure whats going on here. Happens after changing token with workflow
scope to token without workflow
scope.
Hi! I'm currently trying to implement your workflow in https://github.com/voxpupuli/vox-pupuli-tasks/pull/479
from the workflow config:
This fails with:
and a couple of questions: