mayadata-io / mayadata-io/e2e-aws
Grouped jobs in gitlab is based on job numbering instead of name
Open
Nobody has claimed this yet.
gitlab
- Dominant language
- Shell
- Stars
- 0
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading GitLab issues 22918 and 40679 to understand the expected grouping behavior. Then locate the repository's GitLab job definitions and determine which naming or numbering assumptions affect grouping; done means grouped jobs are organized by job name rather than number and the behavior is verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gitlab, shell
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100