Workflows

[github-learning-lab[bot]]

This pull request covers a few common workflows that may be used within your organization.

Challenge question

Suppose you'd like to contribute to the repository pictured below. Which branch should you use as a base for your contributions?

• [x] master
• [ ] release-v1.0
• [ ] bug-fix
• [ ] green-colors
• [ ] config-release-drafter

---

I'll respond when you check one of the boxes above.

[github-learning-lab[bot]]

Answer :crystal_ball:

The real answer is that, without documentation, we don't know!

This pull request covers the basics, but here are some recommendations to help any contributor know the right way to open pull requests:

• Use protected branches. Doing so will allow you to accept pull requests without fear of breaking production code.
• Use CODEOWNERS in combination with protected branches to ensure the right people review changes.
• If you haven't picked a workflow, use a common and well documented one.
• Be explicit about your deployment and release strategy.

:keyboard: Activity: Review workflow documentation

1. Review the changes in the Files changed tab
2. Approve this pull request (if needed)
3. Merge this pull request
4. Delete the branch

---

I'll respond when you merge this pull request.

[github-learning-lab[bot]]

You can find your next steps in your next pull request.