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
As per the title, when Environments are renamed or removed entirely in the config and the app is executed in nop mode via a pull request check run, the environment will be deleted from the associated repositories.
What is actually happening
As per the title, when Environments are renamed or removed entirely in the config and the app is executed in nop mode via a pull request check run, the environment REST endpoint will be sent a DELETE request.
What is the expected behavior
In nop mode no changes should be made to repository settings.
Error output, if available
Not errors, but these logs were generated on a no-op dry run of safe-settings where balena-staging.com+sign-api-key had been deleted from the settings.
Problem Description
As per the title, when Environments are renamed or removed entirely in the config and the app is executed in
nop
mode via a pull request check run, the environment will be deleted from the associated repositories.What is actually happening
As per the title, when Environments are renamed or removed entirely in the config and the app is executed in
nop
mode via a pull request check run, the environment REST endpoint will be sent a DELETE request.What is the expected behavior
In
nop
mode no changes should be made to repository settings.Error output, if available
Not errors, but these logs were generated on a no-op dry run of safe-settings where
balena-staging.com+sign-api-key
had been deleted from the settings.Context
Are you using the hosted instance of probot/settings or running your own?
Self-hosted
If running your own instance, are you using it with github.com or GitHub Enterprise?
github.com
Version of probot/settings
We previously thought this issue had been addressed here: #691
Last reproduced in https://github.com/github/safe-settings/releases/tag/2.1.16
Version of GitHub Enterprise
The text was updated successfully, but these errors were encountered: