sbt / sbt/sbt-github-actions

Stable job names (don't include versions)

Open
#68 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Scala
Stars
199
Forks
67
Avg merge
6h 24m
Merged PRs (30d)
3

Description

Currently the workflow jobs created by this plugin have some parts of the build environment appended to the name, e.g.

Build and Test (ubuntu-latest, 2.13.6, adopt@1.8)

GitHub lets me specify that the jobs must succeed in order to merge a PR - by name:

Required status checks in branch protection rule settings

However, if a PR changes the Scala or Java version it will be problematic to merge without disabling the rule.

In fact, I don't think I'm in control of the Java version or the "ubuntu-latest" part either.

I'd like to have an option to only have the critical pieces of environment (e.g. "Scala 2.13") in the job name, and omit everything else.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points. Start by locating the code that generates workflow job names and any tests covering generated workflow YAML; done means an option can retain critical environment details such as Scala while omitting changing platform and version details.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, scala
Domain
ci-cd
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.