-
Notifications
You must be signed in to change notification settings - Fork 435
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature] Enhancing the Contributing Guide #1034
[Feature] Enhancing the Contributing Guide #1034
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey there @verma-kunal great work here! I've added a few thoughts
``` | ||
6. While submitting Pull Request, **make sure to change the base branch from**: [master](https://github.com/tailwarden/komiser/tree/master) to [develop](v). This will ensure to keep your Pull Request away from any conflicts! | ||
|
||
> ### Keeping your Fork Up-to-Date |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there is a reason for this whole section to be quoted?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the main reason was to highlight this part actually! because merge conflicts can be confusing especially for beginners, so keeping the fork up to date, before committing new changes is always a good practice and prevents merge conflicts
what do you think?
thanks for the suggestions @jakepage91 ! All resolved ✅ |
Thanks @mlabouardy :) |
With this PR, the existing contributing guide has been revamped with the focus on guiding new contributors on the right path to get involved in the Komiser project!
Few noticeable items added:
Reviewers
@jakepage91 @AvineshTripathi
Fixes #1029