open-vault/.github
Ryan Cragun 275479cdd9
[QT-353] Use a different approach to branch restrictions (#17998)
Create a new workflow job that is only triggered when all build and
integration workflows have completed. This will allow us to require
branch restrictions on a single workflow.

Of note, we tried to allow docs branches to bypass testing using the
method suggested by Github[0], however, the `branches-ignore`
functionality did not work for the `pull_request` event type. Therefore,
bypassing build and integration workflows for docs branches is no longer
supported.

[0] https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks#handling-skipped-but-required-checks

Signed-off-by: Ryan Cragun <me@ryan.ec>
2022-11-18 14:43:55 -07:00
..
ISSUE_TEMPLATE Plugin submission GH issue template (#9860) 2020-09-01 17:23:38 -07:00
enos-run-matrices Migrate package_manager smoke test to Enos scenario (#17653) 2022-11-16 14:23:58 -05:00
workflows [QT-353] Use a different approach to branch restrictions (#17998) 2022-11-18 14:43:55 -07:00
CODE_OF_CONDUCT.md add code of conduct (#6049) 2019-01-15 17:30:33 -08:00
ISSUE_TEMPLATE.md Encourage people to use code blocks (#4228) 2018-03-30 17:02:03 -04:00