-
Notifications
You must be signed in to change notification settings - Fork 63
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
feat: adds glossary #211
feat: adds glossary #211
Conversation
Link redirects user to an unavailable page: Issue #181
👷 Deploy request for docs-open pending review.Visit the deploys page to approve it
|
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.
PR Compliance Checks
Thank you for your Pull Request! We have run several checks on this pull request in order to make sure it's suitable for merging into this project. The results are listed in the following section.
Issue Reference
In order to be considered for merging, the pull request description must refer to a specific issue number. This is described in our Contributing Guide.
This check is looking for a phrase similar to: "Fixes #XYZ" or "Resolves #XYZ" where XYZ is the issue number that this PR is meant to address.
Protected Branch
In order to be considered for merging, the pull request changes must not be implemented on the "main" branch. This is described in our Contributing Guide. We would suggest that you close this PR and implement your changes as described in our Contributing Guide and open a new pull request.
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.
Looks great @Lymah123! :)
@Lymah123 you added a setting-up-a-new-repository.md here. I don't think that it is part of the newest Maintainer section. @BekahHW can you confirm this? |
@@ -11,6 +11,11 @@ Pretty often when opening a pull request it is very likely to run into merge con | |||
To better illustrate the commands listed here at will use commits and screenshots from [open-sauced#1078](https://github.com/open-sauced/open-sauced/pull/1078). | |||
|
|||
|
|||
## Repository setup |
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.
@Lymah123 There is a duplication of this title in line 19. Which one do you want to keep?
Also, let's use capital letters for titles. :)
## Repository setup | |
## Repository Setup |
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.
Hi @Lymah123,
I've left some feedback for you here. :)
Also, I pulled your branch and noticed that you worked on your changes on the main
branch.
Please read the PR Compliance Check in the "Protected Branch" section.
Therefore, as per PR Complience Check, I suggest that you:
- Create a new branch and make your changes there.
- Close this PR and create a new PR.
@@ -0,0 +1,33 @@ | |||
# OpenSauced Glossary |
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.
The heading 1
comes from the data. So let's add the data here and not a heading:
# OpenSauced Glossary | |
--- | |
id: glossary | |
title: 'OpenSauced Glossary' | |
sidebar_label: 'OpenSauced Glossary' | |
keywords: | |
- glossary | |
--- | |
## PR Velocity | ||
The PR Velocity measures the percentage and amount of days that pull requests that are merged. It is a great way to track the progress of your open source contributions. |
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.
Let's add a space between the title and paragraph here.
Besides that it is the best practice, we will do this going forward for consistency.
## PR Velocity | |
The PR Velocity measures the percentage and amount of days that pull requests that are merged. It is a great way to track the progress of your open source contributions. | |
## PR Velocity | |
The PR Velocity measures the percentage and amount of days that pull requests that are merged. It is a great way to track the progress of your open source contributions. |
Hi @adiati98 , I didn't change anything from that file. I only touched it due to merge conflicts I had. |
@Lymah123 in that case, I believe it was one of the files from previous version of Maintainers Guide before @BekahHW's newest version. And because you made changes directly in the The StepsHere's what you can do:
|
Description
What type of PR is this? (check all applicable)
Related Tickets & Documents
Mobile & Desktop Screenshots/Recordings
Added tests?
Added to documentation?
[optional] Are there any post-deployment tasks we need to perform?
[optional] What gif best describes this PR or how it makes you feel?