mggeorgiev / mggeorgiev/release-based-workflow
Congratulations
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
## Well done!
Congratulations @mggeorgiev, you've completed the **Creating a Release Based workflow** course!
## During this course you successfully:
- Created a release on GitHub based on a Git tag
- Built an automated project board within your repository to manage your release
- If you look at the board now, everything has moved to the **Done** [column]()
- Created and committed changes on a release branch
- Created a hot fix branch to fix a bug on the release branch
- Installed a Probot app to craft a changelog for your releases
### Keep learning
Want to keep learning? Feel free to [check out our other courses](https://lab.github.com/courses)!
I won't respond to this issue, go ahead and close it when finished!
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
No files, tests, or implementation entry points are mentioned. This issue records completion of the Creating a Release Based workflow course and asks to be closed; no code change is described.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- release
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 10/100