Skip to content
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

Trigger workflow in argus-docker on release #573

Merged

Conversation

johannaengland
Copy link
Contributor

Will trigger the workflow added in Uninett/argus-docker#6.

Another part to close Uninett/argus-docker#4.

To get this to work we need to install a GitHub App that has the permissions to trigger workflows in Argus. This app will be used by the used GitHub action create-github-app-token to create a token with the necessary permissions.

The triggered workflow will take the sent repository name and version number to update its dockerfile
Copy link

@codecov-commenter
Copy link

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 57.34%. Comparing base (ef61bed) to head (696d9e0).

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #573   +/-   ##
=======================================
  Coverage   57.34%   57.34%           
=======================================
  Files          86       86           
  Lines        3692     3692           
  Branches      840      839    -1     
=======================================
  Hits         2117     2117           
  Misses       1566     1566           
  Partials        9        9           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@johannaengland johannaengland merged commit 8403776 into master Sep 4, 2024
3 of 4 checks passed
@johannaengland johannaengland deleted the workflows/trigger-workflow-in-argus-docker-on-release branch September 4, 2024 07:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Make a workflow that builds automated PRs when new back-end or front-end is released
3 participants