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

Improve job names for the build workflow in GitHub Actions #120

Merged

Conversation

mcdonnnj
Copy link
Member

@mcdonnnj mcdonnnj commented Feb 3, 2023

🗣 Description

This pull request improves the names for the test, build, and test-build jobs as displayed in the GitHub web UI. It also sorts all pre-steps keys in a job in descending alphabetical order.

💭 Motivation and context

The key sorting is adjusted to stick as reasonably close to our preference to sort all YAML map keys in alphabetically descending order. Since the steps key is the meat of the job and everything else is configuration it makes sense to have the steps key last and sort everything preceding it in descending alphabetical order.

The job names are updates to both be more descriptive and with the modifications that were required to continue supporting Python 3.6 to make them prettier compared to the auto-generated name using the matrix values.

🧪 Testing

Automated tests pass. You can see the now ✨fabulous✨ output in this run log.

✅ Pre-approval checklist

  • This PR has an informative and human-readable title.
  • Changes are limited to a single goal - eschew scope creep!
  • All relevant type-of-change labels have been added.
  • I have read the CONTRIBUTING document.
  • These code changes follow cisagov code standards.
  • All new and existing tests pass.

@mcdonnnj mcdonnnj added improvement This issue or pull request will add or improve functionality, maintainability, or ease of use test This issue or pull request adds or otherwise modifies test code labels Feb 3, 2023
@mcdonnnj mcdonnnj requested a review from dav3r as a code owner February 3, 2023 19:23
@mcdonnnj mcdonnnj self-assigned this Feb 3, 2023
Copy link
Member

@dav3r dav3r left a comment

Choose a reason for hiding this comment

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

I like it 👍

@mcdonnnj mcdonnnj added the kraken 🐙 This pull request is ready to merge during the next Lineage Kraken release label Feb 8, 2023
Sort all pre-`steps` keys alphabetically descending. Sorting all keys
alphabetically would be somewhat onerous because the `strategy` key
would come after the `steps` key even though it's configuration
information. We can at least sort everything but the `steps` key in
alphabetically descending order and make the `steps` the last for a
job.
Add `name` keys to the `test`, `build`, and `test-build` jobs that are
both more descriptive and include the Python version from the job's
matrix. This will produce consistent and more helpful job names in the
GitHub Actions log in the GitHub web UI.
@mcdonnnj mcdonnnj force-pushed the improvement/update_names_for_jobs_using_matrix_strategy branch from 236f5f6 to 0f3dd39 Compare February 8, 2023 16:17
@jmorrowomni jmorrowomni merged commit 65efbf6 into develop Feb 8, 2023
@jmorrowomni jmorrowomni deleted the improvement/update_names_for_jobs_using_matrix_strategy branch February 8, 2023 16:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
improvement This issue or pull request will add or improve functionality, maintainability, or ease of use kraken 🐙 This pull request is ready to merge during the next Lineage Kraken release test This issue or pull request adds or otherwise modifies test code
Projects
Development

Successfully merging this pull request may close these issues.

4 participants