NatLabRockies / NatLabRockies/api-umbrella
Migrating Code Changes
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 2.2k
- Forks
- 373
- PR merge metrics
- No merged PRs in 30d
Description
Hi, I've noticed that there's no way of editing the public facing site through the UI and that we'd have to have code changes for this. Suppose we make code changes and there's a new release out afterwards. How would we go about migrating our code changes? Input on integrating code changes to future releases would be much appreciated. Thanks.
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
The issue names no files, tests, or entry points, and asks generally how code changes should be migrated across releases. Start by locating the project's release and migration guidance; done would be a documented, repeatable path for carrying custom changes into future releases.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, release
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100