Skip to content

Conversation

@naveen521kk
Copy link
Member

Fix #124
In this PR, I have added contributing guidelines for Dev in ReadMe.

@PgBiel
Copy link
Member

PgBiel commented Jun 3, 2020

Rather, that's what the CONTRIBUTING file is for, not README

@PgBiel PgBiel added documentation Improvements or additions to documentation infrastructure Anything related to our infrastructure labels Jun 3, 2020
@Aathish04
Copy link
Member

Rather, that's what the CONTRIBUTING file is for, not README

@naveen521kk

As @PgBiel said, these instructions should go in the CONTRIBUTING file, not the README

@leotrs
Copy link
Contributor

leotrs commented Jun 3, 2020

@naveen521kk this is a great idea! Please address my comments :)

@leotrs
Copy link
Contributor

leotrs commented Jun 3, 2020

Also, it would be good to include language about pulling from upstream/master right before PRing, resolving merge conflicts locally and only then submitting the PR

Copy link
Member

@PgBiel PgBiel left a comment

Choose a reason for hiding this comment

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

imo, most people here will know how to use Git, so first and foremost we should specify what we want from PRs. More specifically:

  1. If code changes are being made, please include documentation following the guidelines in the Wiki (typings are also welcome, but we can probably do them for you, given the documentation);
  2. (For the maintainers of this repo) Label PRs appropriately;
  3. Link relevant issues;
  4. Ensure compatibility with the latest changes in the repo.

@naveen521kk
Copy link
Member Author

So, should I add it in the top? @PgBiel

@PgBiel
Copy link
Member

PgBiel commented Jun 3, 2020

yes

@naveen521kk naveen521kk requested a review from PgBiel June 3, 2020 14:47
CONTRIBUTING.md Outdated
As this is a Fork of [Manim from 3b1b](https://github.com/3b1b/manim), contributing can be a bit confusing. So here is a small guide on it.

1. First, make a fork of either this Repository.
2. Then clone the repository you forked by the command below.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
2. Then clone the repository you forked by the command below.
2. Then, clone the repository you forked using the command below (bash/zsh).

@naveen521kk naveen521kk requested a review from PgBiel June 3, 2020 15:21
Copy link
Member

@PgBiel PgBiel left a comment

Choose a reason for hiding this comment

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

May I ask what led you to undoing b462fc2?

@naveen521kk naveen521kk requested a review from PgBiel June 5, 2020 04:08
@naveen521kk
Copy link
Member Author

Anything else to be done?

@leotrs
Copy link
Contributor

leotrs commented Jun 5, 2020

Just waiting for @PgBiel 's approval :)

@PgBiel
Copy link
Member

PgBiel commented Jun 5, 2020

May I ask what led you to undoing b462fc2?

@naveen521kk
Copy link
Member Author

naveen521kk commented Jun 5, 2020

I redid it. That was while meging ignored it. Just seen though. @PgBiel It's okay now right?

@PgBiel
Copy link
Member

PgBiel commented Jun 5, 2020

Think so

@PgBiel PgBiel merged commit b000ca6 into ManimCommunity:master Jun 5, 2020
@naveen521kk naveen521kk deleted the contrib-guide branch June 6, 2020 03:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation infrastructure Anything related to our infrastructure

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add contributing Guidelines

4 participants