mitodl / mitodl/release-script
Doof should say that things are taking a long time if a deploy takes more than 30-40 minutes
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 16
- Forks
- 8
- Avg merge
- 11h 47m
- Merged PRs (30d)
- 2
Description
This issue has no 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 locating the deploy progress or status-reporting entry point in the release-script repository. Confirm how elapsed deploy time is tracked, then make the completed work visibly indicate that a deploy has been running for more than 30–40 minutes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100