Defaults are not user-friendly
Open
Nobody has claimed this yet.
- Dominant language
- PLpgSQL
- Stars
- 1.6k
- Forks
- 358
- Avg merge
- 20h 30m
- Merged PRs (30d)
- 27
Description
- Projects are disabled by default when you create them with the UI.
- Jobsets for disabled projects don't evaluate and don't produce any error message that hint at this behaviour.
These two facts create a poor default user experience. As a user I expect that if fill out all the mandatory fields when creating projects and jobsets I either get
- a functional build process
- some errors hinting what went wrong.
Contributor guide
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 tracing how the UI creates projects and jobsets, then follow what happens when a jobset belongs to a disabled project. Done should mean that the default setup produces a functional build process or displays an error explaining that the project is disabled.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100