Skip to content
This repository has been archived by the owner on Jun 24, 2021. It is now read-only.

Update CONTRIBUTING.md to clarify procedures and fix typos #255

Merged
merged 3 commits into from
Oct 22, 2018
Merged

Update CONTRIBUTING.md to clarify procedures and fix typos #255

merged 3 commits into from
Oct 22, 2018

Conversation

kevinrushforth
Copy link
Collaborator

fixes #246

@kevinrushforth
Copy link
Collaborator Author

kevinrushforth commented Oct 20, 2018

As mentioned in #246 the purpose of this PR is to update CONTRIBUTING.md to align with the updated code review guidelines, and to address a few things that I find myself repeating when responding to pull requests from first time developers. I also fixed a few typos and did other light cleanup along the way.

@kevinrushforth kevinrushforth self-assigned this Oct 20, 2018
@kevinrushforth kevinrushforth added the documentation Updates or additions to documentation label Oct 20, 2018
@kevinrushforth
Copy link
Collaborator Author

Note that since this is (currently) a GitHub-only file, there does not need to be a JBS issue since this patch is not destined for the HG repo.

.github/CONTRIBUTING.md Outdated Show resolved Hide resolved
.github/CONTRIBUTING.md Outdated Show resolved Hide resolved
.github/CONTRIBUTING.md Outdated Show resolved Hide resolved

Update your local repository with the most recent code from the main [repository]((https://github.com/javafxports/openjdk-jfx)), and rebase your branch on top of the latest `develop` branch. We prefer your initial changes to be squashed into a single commit. Later, if we ask you to make changes, add them as separate commits. This makes them easier to review. As a final step before merging we will either ask you to squash all commits yourself or we'll do it for you.
If there isn't already a bug filed in [JBS](https://bugs.openjdk.java.net), then please file one at [bugreport.java.com](http://bugreport.java.com/). A JBS bug ID is needed even if you have already filed an issue in the GitHub issue tracker. A GitHub issue can be used as a convenience, but JBS is the official bug database for the OpenJFX Project. Once you submit a pull request, you can add the "github-bug" label on the JBS bug, along with an Issue link to the PR. If you don't have direct JBS access, one of the Project Committers will do this for you.
Copy link

Choose a reason for hiding this comment

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

If you don't have direct JBS access, one of the Project Committers will do this for you.

Authors also have JBS access.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Right, I'll fix this to say "Committers or Authors".

@kevinrushforth
Copy link
Collaborator Author

kevinrushforth commented Oct 22, 2018

For some reason, my last commit didn't trigger a CI build. It might be related to the reported GitHub outage. In any case, all this most recent commit does is add 2 words to a sentence in CONTRIBUTING.md, so we can live without the CI build.

@kevinrushforth
Copy link
Collaborator Author

For some reason, my last commit didn't trigger a CI build. It might be related to the reported GitHub outage.

The outage is reported to be fixed, and the CI builds are in progress, although the Appveyor build hasn't run yet.. I'll merge this in anyway, since any failure would be due to a CI problem not a real problem.

@kevinrushforth kevinrushforth merged commit 125bb5f into javafxports:develop Oct 22, 2018
@kevinrushforth kevinrushforth deleted the fix-contributing branch October 22, 2018 19:19
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
documentation Updates or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Update CONTRIBUTING.md to clarify procedures and fix typos
4 participants