The Wayback Machine - http://web.archive.org/web/20201107150810/https://github.com/expressjs/express/pull/4364
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: Add Submitting a Pull Request (PR) section #4364

Closed
wants to merge 3 commits into from

Conversation

@getspooky
Copy link
Member

@getspooky getspooky commented Jul 27, 2020

Hello,
I think , it's good idea to provide short guideline on how to submit a pull request on expressjs repo.
This section could useful for new contributors .

@getspooky getspooky requested a review from dougwilson Jul 27, 2020
Copy link
Member

@dougwilson dougwilson left a comment

Can you enhance the existing docs in https://github.com/expressjs/express/blob/master/Collaborator-Guide.md instead of creating a duplicate location for this information?

@getspooky getspooky force-pushed the getspooky:my-branch-docs branch from 6e2c84c to d157f99 Jul 27, 2020
@getspooky
Copy link
Member Author

@getspooky getspooky commented Jul 27, 2020

Hi @dougwilson
Feel free to check my PR. Any Suggestion ?


1. Search [GitHub](https://github.com/expressjs/express/pulls) for an open or closed PR that relates to your submission. You don't want to duplicate effort.

2. [Create an issue](https://github.com/expressjs/express/issues/new) for the

This comment has been minimized.

@dougwilson

dougwilson Jul 27, 2020
Member

If the user is about to submit a PR, it would be best to not open an issue then open a PR. The issue this creates is that some folks may start working on the PR, but the opener was already working on it. I suggest a user either open a PR or an issue, but not both.

a pull request from there. Make sure to reference your issue from the pull
request comments by including the issue number e.g. `#123`.

3. Fork the `expressjs/express` repo.

This comment has been minimized.

@dougwilson

dougwilson Jul 27, 2020
Member

What us wrong with the existing wording of the step? It seems more helpful before.

7. Run the full expressjs test suite , and ensure that all tests pass :

```shell
npm run test

This comment has been minimized.

@dougwilson

dougwilson Jul 27, 2020
Member

This is just npm test

git commit -a
```

Note: the optional commit `-a` command line option will automatically "add" and "rm" edited files.

This comment has been minimized.

@dougwilson

dougwilson Jul 27, 2020
Member

The -a does not rm any files, so I think this is misleading.

git push origin my-fix-branch
```

10. In GitHub, Send a pull request to `expressjs:master`

This comment has been minimized.

@dougwilson

dougwilson Jul 27, 2020
Member

This is not always the case. I believe there is docs in here for the branches used.


- Make the required updates.

- Re-run the expressjs test suites to ensure tests are still passing.

This comment has been minimized.

@dougwilson

dougwilson Jul 27, 2020
Member

expressjs is the org name, I would probably just say test suites here.

Collaborator-Guide.md Outdated Show resolved Hide resolved

5. Create your patch, **including appropriate test cases**.

6. Install the dependencies by running :

This comment has been minimized.

@dougwilson

dougwilson Jul 28, 2020
Member

Suggested change
6. Install the dependencies by running :
6. Install the dependencies by running:

fixed spacing

4. Make your changes in a new git branch:

```shell
git checkout -b my-fix-branch master

This comment has been minimized.

@dougwilson

dougwilson Jul 28, 2020
Member

Can you clarify at what indent level you are intending these blocks to be at? They start at two spaces, then a couple down just one space, and then ended with no spaces.

Co-authored-by: Douglas Wilson <67512+dougwilson@users.noreply.github.com>
Copy link
Member Author

@getspooky getspooky left a comment

Update Collaborator-Guide

Co-authored-by: Douglas Wilson <67512+dougwilson@users.noreply.github.com>
@dougwilson
Copy link
Member

@dougwilson dougwilson commented Sep 17, 2020

I'm going to close for now to help clean up, as it has been several months and no fixes to the noted issue or even replies to them.

@dougwilson dougwilson closed this Sep 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

2 participants
You can’t perform that action at this time.