Skip to content
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

Docs: added a Pull Request Guidelines in CONTRIBUTING.md #1520

Merged
merged 15 commits into from
Nov 6, 2020
Merged
Changes from 11 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -109,6 +109,23 @@ Note the path must start with must start with a `.` to be considered local

The `--verbose` flag enables additional logs which will help to identify the source of a problem. The `--reload` will clear the local cache which might have been created by a different `snowpack` version. Learn more about [Snowpack's CLI flags](https://www.snowpack.dev/#cli-flags).

## Pull Request Guidelines

- Checkout a topic branch from a base branch, e.g. `master`, and merge back against that branch.

- If adding a new feature:

- Provide a convincing reason to add this feature.
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If adding a feature, it probably should have been brought up in a "discussion" instead before the PR was created. If you're having to convince anyone that the feature is a good idea at the PR stage, it's probably too late (I have closing PRs that could have been fleshed out more as discussions)

- Add accompanying tests if applicable.

- If fixing bug:

- If you are resolving a special issue, add `(fix #xxxx)` (#xxxx is the issue id) in your PR title for a better release.
Copy link
Owner

@FredKSchott FredKSchott Nov 5, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you can frame these as more "recommended" than "required", that would be great. Something like this format:

Checkout a topic branch from a base branch, e.g. master, and merge back against that branch.

Some tips for creating your first pull request:

  • Provide background for why a PR was created.
  • Link to any relevant issues, discussions, or past PRs
  • ...

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have followed your advice. Checked it please if you are free.

- Provide a detailed description of the bug in the PR. Live demo preferred.
- Add appropriate tests if applicable.

- Ensure all tests have been passed.

## Discussion

[Join the Pika Discord](https://discord.gg/rS8SnRk)