-
-
Notifications
You must be signed in to change notification settings - Fork 220
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
Run rake sync_github_advisories
as a scheduled workflow
#537
Comments
Please feel free to contribute a workflow. I will note that the current script isn't as easy as it might seem. Still a lot of manual work to take the output and get the advisories in order. |
I've attempted to get this working in https://github.com/ddalcino/ruby-advisory-db/tree/sync_github_advisories, but I keep running into credential problems. I can run the Here's the stack trace from this build: https://github.com/ddalcino/ruby-advisory-db/actions/runs/4109381580/jobs/7091810877
|
Try using |
I have added the - name: Sync with Github Advisories
env:
GH_API_TOKEN: ${{ secrets.GH_API_TOKEN }}
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
run: bundle exec rake sync_github_advisories ... and I'm still seeing the same 'Bad credentials' error:
|
I meant this: - name: Sync with Github Advisories
env:
GH_API_TOKEN: ${{ secrets.GITHUB_TOKEN }}
run: bundle exec rake sync_github_advisories GH_API_TOKEN is needed here: ruby-advisory-db/lib/github_advisory_sync.rb Lines 172 to 181 in 38305c6
But the value will come from |
I noticed that a significant fraction of the commit history of this project looks like automated changes on the part of the
rake sync_github_advisories
task. Yesterday, while the maintainers were dealing with #536, I had the impression that running this task manually was a burdensome chore. I think that this task could be made easier using a Github Actions workflow.If you are interested, I can contribute a PR for a workflow that will automatically run the rake task and submit a PR if any new advisories were added. This workflow could be triggered manually by clicking a button in the Github UI, or it could run on a schedule like a cron job.
Please let me know what you think.
The text was updated successfully, but these errors were encountered: