-
Notifications
You must be signed in to change notification settings - Fork 30
docs: adjust README.md and CONTRIBUTING.md #279
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: adjust README.md and CONTRIBUTING.md #279
Conversation
CONTRIBUTING.md
Outdated
| ### Merging PRs | ||
|
|
||
| - Before a PR is merged, all commits in the PR should be rebased into meaningful commits. | ||
| - Before a PR is merged, all commits in the PR should meaningful commits. |
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.
| - Before a PR is merged, all commits in the PR should meaningful commits. | |
| - Before a PR is merged, all commits in the PR should have meaningful commits. |
We could use another word if it make more sense.
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.
See commit 6de60e8
|
|
||
| * The `main` branch is only used for releases and the `staging` branch is used for development. We only merge to `main` when we want to create a new release for Macaron. | ||
|
|
||
| ## Setting up the development environment |
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.
Could you rebase on staging and update the reference to this section in docs/README.md - https://github.com/oracle-samples/macaron/blob/e6656c486f956e843e250d8dec3ace0bf36a2ecb/docs/README.md?plain=1#L7
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.
See commit 6de60e8
CONTRIBUTING.md
Outdated
| ``` | ||
|
|
||
| ### Obtaining the GitHub personal access token | ||
| Create your own Github access token (please refer to the instructions [here](https://docs.github.com/en/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)). When creating this token, make sure to assign **at least** `repo` permissions. |
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.
I think we can update the instruction on permission of the Github token by using parts of the instructions we have for the Sphinx documentation
Ideally, the GitHub token must have read permissions for the repositories that you want to analyze:
- Every fine-grained personal-access token should have read permission to public GitHub repositories. However, if you are analyzing a private repository, please select it in the Repository Access section.
- For classic personal-access token, the repo.public_repo scope must be selected. Please select the whole repo scope if you are running the analysis against private repositories.
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.
See commit 6de60e8
Signed-off-by: behnazh-w <behnaz.hassanshahi@oracle.com>
Signed-off-by: behnazh-w <behnaz.hassanshahi@oracle.com>
e46dc4e to
6de60e8
Compare
Signed-off-by: behnazh-w <behnaz.hassanshahi@oracle.com>
Closes #275 and #272