Skip to content

Latest commit

 

History

History
53 lines (30 loc) · 3.16 KB

CONTRIBUTING.md

File metadata and controls

53 lines (30 loc) · 3.16 KB

Welcome to Product-Micro contributing guide

Thank you for investing your time in contributing to my project! 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

See the README to get an overview of the project. Here are some helpful resources to get you comfortable with open source contribution:

Getting started

See the introduction authentication microservice in golang to understand the Authentication Microservice.

Before making changes, see what types of contributions we accept. Some of them don't require writing even a single line of code ✨.

Issues

Create a new issue

If you spot a problem with the code or logic, please search if the issue already exists. If a related issue doesn't exist, you can open a new issue.

Solve an issue

Scan through our existing issues to find one that interests you. You can narrow down the search using labels as filters. This repository is participating in HacktoberFest. Your Approved Pull Request will contribute to the fest.

Make Changes

Make changes in the UI

Click Make a contribution at the bottom of any docs page to make small changes such as a typo, sentence fix, or a broken link. This takes you to the .md file where you can make your changes and create a pull request for a review.

Pull Request

This Repository is taking part in HacktoberFest. If your PR gets approved, it will be reflected on your HacktoberFest DashBoard.

When you're done making the changes, open a pull request, often referred to as a PR.

  • Fill out the "Ready for review" template so we can review your PR. This template helps reviewers understand your changes and the purpose of your pull request.
  • Don't forget to link PR to issue if you are solving one.
  • Once you submit your PR, a I will review your proposal. I may ask a few basic questions or request for additional information. Make sure the Pull Request you make for a new feature are followed by creation of an Issue.
  • 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!

Once your PR is merged, your contributions will be publicly visible on the project