You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The "Update Template CI" workflow appears successful even when a repository rule prevents writing the update to the repository.
A few months ago I converted all of our repositories to use org-level rulesets, but this overrode our Upptime repository exception for our bot user to commit to the master branch. I did not notice this until months later when the "Uptime CI" workflow started failing due to a Node version conflict. After further investigation, I saw that the Node issue had been resolved in the latest release but the "Update Template CI" workflow had been failing.
I imagine the "Uptime CI" and other workflows have a similar issue since none of them failed to push in the months since I broke things.
To Reproduce
Setup Upptime
Set GH_PAT to a token that has the appropriate access
Enable a branch rule on master that requires pull requests
Run "Update Template CI"
Expected behavior
The workflow should fail with an error rather than succeed.
Screenshots
Desktop (please complete the following information):
OS: Windows
Browser: Brave
Version: 1.67.123
Additional context
N/A
The text was updated successfully, but these errors were encountered:
Describe the bug
The "Update Template CI" workflow appears successful even when a repository rule prevents writing the update to the repository.
A few months ago I converted all of our repositories to use org-level rulesets, but this overrode our Upptime repository exception for our bot user to commit to the
master
branch. I did not notice this until months later when the "Uptime CI" workflow started failing due to a Node version conflict. After further investigation, I saw that the Node issue had been resolved in the latest release but the "Update Template CI" workflow had been failing.I imagine the "Uptime CI" and other workflows have a similar issue since none of them failed to push in the months since I broke things.
To Reproduce
GH_PAT
to a token that has the appropriate accessmaster
that requires pull requestsExpected behavior
The workflow should fail with an error rather than succeed.
Screenshots
Desktop (please complete the following information):
Additional context
N/A
The text was updated successfully, but these errors were encountered: