We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently, the PR-action workflow explicitly lists /fix action names. We should keep things DRY and instead check via:
/fix
$ npm run -s _list:fix:\* fix:dict fix:expired fix:filenames fix:format fix:htmltest-config fix:i18n fix:markdown fix:refcache fix:submodule fix:text
Though that would probably require something like renaming fix:refcache:refresh to a direct fix argument, such as fix:refcache-refresh. Such an approach would avoid script-name mismatches as what occurred in https://github.com/open-telemetry/opentelemetry.io/actions/runs/12654515860/job/35262586821.
fix:refcache:refresh
fix
fix:refcache-refresh
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Currently, the PR-action workflow explicitly lists
/fix
action names. We should keep things DRY and instead check via:Though that would probably require something like renaming
fix:refcache:refresh
to a directfix
argument, such asfix:refcache-refresh
. Such an approach would avoid script-name mismatches as what occurred in https://github.com/open-telemetry/opentelemetry.io/actions/runs/12654515860/job/35262586821.The text was updated successfully, but these errors were encountered: