Skip to content

Latest commit

 

History

History
71 lines (42 loc) · 4.85 KB

contributing.md

File metadata and controls

71 lines (42 loc) · 4.85 KB
Raw

Welcome to TCET Linux contributing guide

Thank you for investing your time in contributing to our project! Any contribution you make will be reflected from our next release ✨.

Read our Code of Conduct to keep our community approachable and respectable.

In this guide you will get an overview of the contribution workflow from opening an issue, creating a PR, reviewing, and merging the PR.

New contributor guide

To get an overview of the project, read the README file. Here are some resources to help you get started with open source contributions:

Getting started

To navigate our codebase with confidence, see documentation of TCET Linux 🎊.

Issues

Create a new issue

If you spot a problem, search if an issue already exists. If a related issue doesn't exist, you can open a new issue using a relevant issue form.

Solve an issue

  1. Scan through our existing issues to find one that interests you. You can narrow down the search using labels as filters.

  2. See Good First Issues label for beginner issues.

  3. Leave a comment to get it assigned.

Make Changes

  1. Fork the repository.

  1. Install or update archiso, for creating ISO. For more information, see How to build ISO.

  2. Create a working branch and start with your changes!

Commit your update

Commit the changes once you are happy with them. Don't forget to self-review to speed up the review process:zap:.

Pull Request

When you're finished with the changes, create a pull request, also known as a PR.

  • 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.
  • Don't forget to link PR to issue if you are solving one.
  • Enable the checkbox to allow maintainer edits so the branch can be updated for a merge. Once you submit your PR, a DevOps team member will review your proposal. We may ask questions or request additional information.
  • 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.
  • If you run into any merge issues, checkout this git tutorial to help you resolve merge conflicts and other issues.

Your PR is merged!

Congratulations 🎉🎉 The DevOps team thanks you ✨.

Once your PR is merged, your contributions will be visible on the TCET Linux.

Now that you are part of the TCET-Opensource community, see how else you can contribute to the TCET-Opensource.