Before you begin:
- Join the Slack channel #open-source-project-work in the LaunchCode Community Slack Workspace.
- Get familiar with working on open source projects with our Open Source Starter Pack
- Have you read the Collab-Blog README?
- Have you read the Collab Blog Code of Conduct?
- Check out the existing issues
Before you make your changes, check to see if an issue exists already for the change you want to make.
If you spot something new, open an issue using a template. We'll use the issue to have a conversation about the problem you want to fix.
Follow the instruction in the README to set up your development environment.
Make your changes to the file(s) you'd like to update.
When you're done making changes and you'd like to propose them for review, open a pull request and fill out the template in the body of the PR with a refernece to the related issue (You can bring up a list of suggested issues by typing #. Type the issue number or title to filter the list, and then press either tab or enter to complete the highlighted result.), a discription of the changes proposed and tag @rrolon47 and @jwoolbright23 to review proposed changes.
- Once you submit your PR, admin will review it with you. The first thing you're going to want to do is a self review.
- After that, we may have questions, check back on your PR to keep up with the conversation.
- Did you have an issue, like a merge conflict? Check out GitHub's git tutorial on how to resolve merge conflicts and other issues.
///
Congratulations! The whole Collab-Blog community thanks you! ✨
Once your PR is merged, you will be proudly listed as a contributor in the contributor chart.
Now that you're a part of the Collab-Blog community, you can keep participating in many ways.
Learn more about contributing:
You can browse existing issues to find something that needs help!
Labels can help you find an issue you'd like to help with. Find out what lables mean here.
You can use the GitHub user interface ✏️ for some small changes, like fixing a typo or updating a readme. You can also fork the repo and then clone it locally, to view changes and run your tests on your machine.
We review every single PR.
💛 Reviews are always respectful, acknowledging that everyone did the best possible job with the knowledge they had at the time.
💛 Reviews discuss content, not the person who created it.
💛 Reviews are constructive and start conversation around feedback.
You should always review your own PR first.
For content changes, make sure that you:
- Confirm that the changes meet the user experience and goals outlined in the issue you are addressing.
- Run and review the changes to make sure the program still runs.
- Copy-edit the changes for grammar and spelling.
- If there are any failing checks in your PR, troubleshoot them until they're all passing.
When you open a pull request, you must fill out the issue number and the changes made before we can review your PR. This template helps reviewers understand your changes and the purpose of your pull request.
We may ask for changes to be made before a PR can be merged, either using suggested changes or pull request comments. You can apply suggested changes directly through the UI. You can make any other changes in your fork, then commit them to your branch.
As you update your PR and apply changes, mark each conversation as resolved.