Skip to content

Conversation

@dscho
Copy link
Member

@dscho dscho commented Feb 13, 2025

Since #29 GitForWindowsHelper has not triggered any Azure Pipeline.

The main reason why some of the settings are disabled in this script is
so that no state is changed on github.com when debugging a webhook
payload event locally.

However, in some cases the GitForWindowsHelper app needs to query
GitHub's REST API using an access token because some queries cannot be
issued without authorization. For example, for some reason or other
reading workflow runs' logs requires a token (which is different than
what Azure Pipelines does, from which GitHub Actions were derived, so
this is doubly curious).

To help with such debugging scenarios, have a separate way to prevent
specifically triggering workflow runs, which would be the worst thing to
do inadvertently during a debugging session.

By default, the private key and Azure Pipelines trigger token are still
disabled in the script, but now it is at least somewhat safe to comment
out the private key disabling so that above-mentioned queries can be
debugged locally.

Signed-off-by: Johannes Schindelin <[email protected]>
Git for Windows has been using GitHub workflows instead, ever since
#29 was
merged.

Therefore, the code to trigger Azure Pipelines has not been in use for
almost two years. It's time to retire it.

Signed-off-by: Johannes Schindelin <[email protected]>
@dscho dscho requested review from mjcheetham and rimrul February 13, 2025 14:51
@dscho dscho self-assigned this Feb 13, 2025
@dscho dscho merged commit adc1a0e into main Feb 13, 2025
1 check passed
@dscho dscho deleted the retire-the-azure-pipeline-trigger branch February 13, 2025 16:15
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.

3 participants