|
| 1 | +# Welcome to TCET Linux contributing guide |
| 2 | + |
| 3 | +Thank you for investing your time in contributing to our project! Any contribution you make will be reflected from our next release :sparkles:. |
| 4 | + |
| 5 | +Read our [Code of Conduct](https://github.com/tcet-opensource/.github/blob/main/CODE_OF_CONDUCT.md) to keep our community approachable and respectable. |
| 6 | + |
| 7 | +In this guide you will get an overview of the contribution workflow from opening an issue, creating a PR, reviewing, and merging the PR. |
| 8 | + |
| 9 | +## New contributor guide |
| 10 | + |
| 11 | +To get an overview of the project, read the [README](https://github.com/tcet-opensource/tcet-linux/blob/main/README.md) file. Here are some resources to help you get started with open source contributions: |
| 12 | + |
| 13 | +- [Contributing to TCET-Opensource Externally](https://opensource.tcetmumbai.in/docs/resources/workflows/external-workflow/) |
| 14 | +- [Set up Git](https://docs.github.com/en/get-started/quickstart/set-up-git) |
| 15 | +- [GitHub flow](https://docs.github.com/en/get-started/quickstart/github-flow) |
| 16 | + |
| 17 | + |
| 18 | +## Getting started |
| 19 | + |
| 20 | +To navigate our codebase with confidence, see documentation of [TCET Linux](https://opensource.tcetmumbai.in/docs/projects/tcet-linux/about-tcet-linux/) :confetti_ball:. |
| 21 | + |
| 22 | +### Issues |
| 23 | + |
| 24 | +#### Create a new issue |
| 25 | + |
| 26 | +If you spot a problem, [search if an issue already exists](https://github.com/tcet-opensource/tcet-linux/issues). If a related issue doesn't exist, you can open a new issue using a relevant [issue form](https://github.com/tcet-opensource/tcet-linux/issues). |
| 27 | + |
| 28 | +#### Solve an issue |
| 29 | + |
| 30 | +1. Scan through our [existing issues](https://github.com/tcet-opensource/tcet-linux/issues) to find one that interests you. You can narrow down the search using `labels` as filters. |
| 31 | + |
| 32 | +2. See [Good First Issues](https://github.com/tcet-opensource/tcet-linux/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22) label for beginner issues. |
| 33 | + |
| 34 | +3. Leave a comment to get it assigned. |
| 35 | + |
| 36 | +### Make Changes |
| 37 | + |
| 38 | +1. Fork the repository. |
| 39 | +- Using GitHub Desktop: |
| 40 | + - [Getting started with GitHub Desktop](https://docs.github.com/en/desktop/installing-and-configuring-github-desktop/getting-started-with-github-desktop) will guide you through setting up Desktop. |
| 41 | + - Once Desktop is set up, you can use it to [fork the repo](https://docs.github.com/en/desktop/contributing-and-collaborating-using-github-desktop/cloning-and-forking-repositories-from-github-desktop)! |
| 42 | + |
| 43 | +- Using the command line: |
| 44 | + - [Fork the repo](https://docs.github.com/en/github/getting-started-with-github/fork-a-repo#fork-an-example-repository) so that you can make your changes without affecting the original project until you're ready to merge them. |
| 45 | + |
| 46 | +2. Install or update **archiso**, for creating ISO. For more information, see [How to build ISO](https://github.com/tcet-opensource/tcet-linux/tree/main#how-to-build-iso). |
| 47 | + |
| 48 | +3. Create a working branch and start with your changes! |
| 49 | + |
| 50 | +### Commit your update |
| 51 | + |
| 52 | +Commit the changes once you are happy with them. Don't forget to [self-review](/contributing/self-review.md) to speed up the review process:zap:. |
| 53 | + |
| 54 | +### Pull Request |
| 55 | + |
| 56 | +When you're finished with the changes, create a pull request, also known as a PR. |
| 57 | +- Fill the PR template so that we can review your PR. This template helps reviewers understand your changes as well as the purpose of your pull request. |
| 58 | +- Don't forget to [link PR to issue](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue) if you are solving one. |
| 59 | +- Enable the checkbox to [allow maintainer edits](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork) so the branch can be updated for a merge. |
| 60 | +Once you submit your PR, a DevOps team member will review your proposal. We may ask questions or request additional information. |
| 61 | +- We may ask for changes to be made before a PR can be merged, either using [suggested changes](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request) 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. |
| 62 | +- As you update your PR and apply changes, mark each conversation as [resolved](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request#resolving-conversations). |
| 63 | +- If you run into any merge issues, checkout this [git tutorial](https://github.com/skills/resolve-merge-conflicts) to help you resolve merge conflicts and other issues. |
| 64 | + |
| 65 | +### Your PR is merged! |
| 66 | + |
| 67 | +Congratulations :tada::tada: The DevOps team thanks you :sparkles:. |
| 68 | + |
| 69 | +Once your PR is merged, your contributions will be visible on the [TCET Linux](https://github.com/tcet-opensource/tcet-linux). |
| 70 | + |
| 71 | +Now that you are part of the TCET-Opensource community, see how else you can [contribute to the TCET-Opensource](https://opensource.tcetmumbai.in/docs/resources/workflows/external-workflow). |
0 commit comments