ministryofjustice / ministryofjustice/developer-experience-github-audit
[Dashboard Expansion] - Identify Reference Opportunities from github-community
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2
- Forks
- 2
- Avg merge
- 10d 5h
- Merged PRs (30d)
- 2
Description
👀 Why are we Doing this?
- As a - I want - So That -
🔧 Engineering Context and Background (Optional)
- The solution should align with our teams agreed Ways of Engineering.
📝 Notes (Optional)
✅ Definition of Done
- Document outcome, where appropriate
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
The issue does not name any files, tests, or entry points, and its purpose and implementation details are still blank. Start by clarifying what “reference opportunities” from github-community means and where the dashboard change belongs. Done is currently limited to documenting the outcome, where appropriate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100