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
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This PR restructures the GH actions into two jobs.
First one runs and executes arbitrary code, and is by nature unsafe. It ends with creating a diff patch, and does not have any write permissions to anything.
The second job is not user extensible, and applies the diff to the source branch of the PR.
The following comments in a PR can be used as commands to execute scripts which automate repository maintenance and make it part of the visible diff.
/run fantomas runs dotnet fantomas .
/run ilverify updates IL verification baseline
/run xlf refreshes localisation files for translatable strings
/run test-baseline ... runs tests with the TEST_UPDATE_BSL: 1 environment variable and an argument supplied filter (passed to dotnet test --filter ..). Its goal is to refresh baselines.
@edgarfgp , @auduchinok : Are there other types of content changes that would also made use of a command, and would not be covered by the above?
Will have to figure out how to do it without a dummy commit (my current naive idea) and without risks with exposing the access token. Will check how this is done elsewhere.
Will have to figure out how to do it without a dummy commit (my current naive idea) and without risks with exposing the access token. Will check how this is done elsewhere.
AFAIK it never worked for OSS contributors, who also do not have the "rerun" buttons when seeing the Checks tab on a PR. @edgarfgp : What happens when you try /azp run please?
AFAIK it never worked for OSS contributors, who also do not have the "rerun" buttons when seeing the Checks tab on a PR. @edgarfgp : What happens when you try /azp run please?
Correct, but what if it's person's own PR? I thought arcade folks fixed it - that you can rerun own PR.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR restructures the GH actions into two jobs.
First one runs and executes arbitrary code, and is by nature unsafe. It ends with creating a diff patch, and does not have any write permissions to anything.
The second job is not user extensible, and applies the diff to the source branch of the PR.
The following comments in a PR can be used as commands to execute scripts which automate repository maintenance and make it part of the visible diff.
/run fantomasrunsdotnet fantomas ./run ilverifyupdates IL verification baseline/run xlfrefreshes localisation files for translatable strings/run test-baseline ...runs tests with theTEST_UPDATE_BSL: 1environment variable and an argument supplied filter (passed todotnet test --filter ..). Its goal is to refresh baselines.@edgarfgp , @auduchinok : Are there other types of content changes that would also made use of a command, and would not be covered by the above?