Skip to content
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

[github] GitHub Actions workflows changes #65856

Merged
merged 1 commit into from
Sep 12, 2023

Conversation

VoltrexKeyva
Copy link
Member

  • Remove usages of the non-existent ignore-forks field, conditions in jobs already exist to prevent the jobs from running in forks.
  • Don't use variables in the printf format string. Use printf "..%s.." "$foo". (SC2059)
  • Double quote variable expansion to prevent globbing and word splitting. (SC2086)
  • Prefer [ p ] || [ q ] as [ p -o q ] is not well defined. (SC2166)
  • Consider { cmd1; cmd2; } >> file instead of individual redirects. (SC2129)
  • Use $(...) notation instead of legacy notation .... (SC2006)
  • Use ./*glob* or -- *glob* so names with dashes won't become options. (SC2035)
  • Refactor JavaScript code in certain workflows.
  • Change workflow variable substitution style of some workflows to be consistent with others.

- Remove usages of the non-existent `ignore-forks` field, conditions in
jobs already exist to prevent the jobs from running in forks.
- Don't use variables in the `printf` format string. Use `printf
"..%s.." "$foo"`. ([SC2059](https://www.shellcheck.net/wiki/SC2059))
- Double quote variable expansion to prevent globbing and word
splitting. ([SC2086](https://www.shellcheck.net/wiki/SC2086))
- Prefer `[ p ] || [ q ]` as `[ p -o q ]` is not well defined.
([SC2166](https://www.shellcheck.net/wiki/SC2166))
- Consider `{ cmd1; cmd2; } >> file` instead of individual redirects.
([SC2129](https://www.shellcheck.net/wiki/SC2129))
- Use `$(...)` notation instead of legacy notation `...`.
([SC2006](https://www.shellcheck.net/wiki/SC2006))
- Use `./*glob*` or `-- *glob*` so names with dashes won't become
options. ([SC2035](https://www.shellcheck.net/wiki/SC2035))
- Refactor JavaScript code in certain workflows.
- Change workflow variable substitution style of some workflows to be
consistent with others.
@VoltrexKeyva VoltrexKeyva requested a review from a team as a code owner September 9, 2023 18:00
Copy link
Collaborator

@tstellar tstellar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good, have you tested it?

@tru
Copy link
Collaborator

tru commented Sep 12, 2023

Yeah I don't mind these changes as long as they work correctly.

@VoltrexKeyva
Copy link
Member Author

Yes, they work correctly.

@VoltrexKeyva VoltrexKeyva merged commit 859e6aa into llvm:main Sep 12, 2023
3 checks passed
@VoltrexKeyva VoltrexKeyva deleted the workflow-changes branch September 12, 2023 22:21
ZijunZhaoCCK pushed a commit to ZijunZhaoCCK/llvm-project that referenced this pull request Sep 19, 2023
- Remove usages of the non-existent `ignore-forks` field, conditions in
jobs already exist to prevent the jobs from running in forks.
- Don't use variables in the `printf` format string. Use `printf
"..%s.." "$foo"`. ([SC2059](https://www.shellcheck.net/wiki/SC2059))
- Double quote variable expansion to prevent globbing and word
splitting. ([SC2086](https://www.shellcheck.net/wiki/SC2086))
- Prefer `[ p ] || [ q ]` as `[ p -o q ]` is not well defined.
([SC2166](https://www.shellcheck.net/wiki/SC2166))
- Consider `{ cmd1; cmd2; } >> file` instead of individual redirects.
([SC2129](https://www.shellcheck.net/wiki/SC2129))
- Use `$(...)` notation instead of legacy notation `...`.
([SC2006](https://www.shellcheck.net/wiki/SC2006))
- Use `./*glob*` or `-- *glob*` so names with dashes won't become
options. ([SC2035](https://www.shellcheck.net/wiki/SC2035))
- Refactor JavaScript code in certain workflows.
- Change workflow variable substitution style of some workflows to be
consistent with others.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants