-
Notifications
You must be signed in to change notification settings - Fork 106
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
docs(workflow): adds a description at the top of each file #8009
Conversation
Ah, sorry about that, I added descriptions as part of the external repository patch PRs, because it was starting to get really confusing. |
Co-authored-by: Marek <[email protected]>
I think there are bugs in this branch that are fixed in the base PR, so I just updated it. |
Ah, that doesn't seem to work, maybe the bugs are still in the base PR. |
* ref(workflow): move most scripts to their own executable * debug: JSON value * fix(scripts): move remaining script to its own file * fix(script): revert to the correct disk search logic * fix(scripts) * fix(scripts): use correct NETWORK with lowercase * fix: typo * fix(script): wrong variable assignment * fix(script): use correct return values inside a function * fix(script): fix value assigment * test: debug * fix(script): make disk conditions simpler * fix(script): export variables to the `shell` executing the script * fix(script): do not fail on expected unbound variables * test: output * fix(scripts): do not `echo` a variable more than once * fix(scripts): typo * docs(workflow): adds a description at the top of each file (#8009) Co-authored-by: Marek <[email protected]> Co-authored-by: teor <[email protected]> --------- Co-authored-by: teor <[email protected]> Co-authored-by: Alfredo Garcia <[email protected]> Co-authored-by: Marek <[email protected]>
Motivation
It's better if member of the team, existing or new contributors, can understand what a workflow file is meant to do (overall) before deep diving into it and trying to understand it piece by piece.
Closes #7607
Depends-On: #8009
PR Author Checklist
Check before marking the PR as ready for review:
For significant changes:
If a checkbox isn't relevant to the PR, mark it as done.
Solution
Review
This PR depends on changes on the scrips, so I didn't had to make these changes twice.
Reviewer Checklist
Check before approving the PR:
PR blockers can be dealt with in new tickets or PRs.
And check the PR Author checklist is complete.
Follow Up Work
None