deal with automatic updates automatically
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 2k
- Forks
- 511
- Avg merge
- 11h 23m
- Merged PRs (30d)
- 2
Description
following this slack thread, we currently need to manually notify admissions teams and teachers so that the students avoid to upgrade their operating system during a batch
a solution could be :
- add a step in the setup to disable automatic updates
- send a slack message after the demo day to tell students how to restore the updates
- potentially add a helper setup to deal with os upgrades (post bootcamp)
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 the linked Slack thread and the repository's setup instructions to understand the batch constraints and current manual notifications. Decide which of the proposed paths is in scope: disabling updates during setup, notifying students after demo day, or adding a post-bootcamp helper. Done means the chosen workflow prevents disruptive upgrades during a batch and documents how updates are restored.
Written by the indexing model from the issue text.
Assessment
- Domain
- devops, operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100