-
Notifications
You must be signed in to change notification settings - Fork 162
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
ci: use best practice #331
Conversation
63f55f9
to
b0e2bc6
Compare
b0e2bc6
to
be24f78
Compare
be24f78
to
ccc0a58
Compare
ccc0a58
to
6fccd4d
Compare
6fccd4d
to
f6fb617
Compare
ab28ad8
to
7d61b27
Compare
7d61b27
to
ba5b543
Compare
a43d0cf
to
ba5b543
Compare
@rmehta Could you please adapt the branch protection rules to check for the updated ci actions? |
Updated your role to "maintain"
… On 02-Oct-2024, at 2:57 PM, David Arnold ***@***.***> wrote:
@rmehta <https://github.com/rmehta> Could you please adapt the branch protection rules to check for the updated checks? Server is old and test have been broken anyway for months. I fixed them here.
—
Reply to this email directly, view it on GitHub <#331 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABCGLESOY5ZD4JEJTFWRITZZO37HAVCNFSM6AAAAABPGXVDKCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOBYGAZDGMRXGQ>.
You are receiving this because you were mentioned.
|
@rmehta Thanks, unfortunately, that doesn't seem to be "enough" for this configuration. I don't want to escalate my privileges too much, so I'd be very happy if someone from staff could have a quick look:
|
updated. check? also updated you to "admin" |
No description provided.