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

chore: Update repo README and CONTRIBUTING section #1439

Merged
merged 4 commits into from
Dec 6, 2023

Conversation

heitortsergent
Copy link
Collaborator

What?

A little bit more cleanup work to make it easier to contribute to the docs after our migration to the Grafana website. :)

  • Update the repo README to more clearly link to Writers' Toolkit and CONTRIBUTING sections.
  • Update the CONTRIBUTING/README to explain where to make updates (copying over information from the Pull Request template), how to use the apply-patch script, and the steps for creating a new release folder.
  • Update the Pull Request template file to link to how to use the apply-patch script section in the CONTRIBUTING file.

Checklist

Please fill in this template:

  • I have used a meaningful title for the PR.
  • I have described the changes I've made in the "What?" section above.
  • I have performed a self-review of my changes.

Add more details about where to make changes, apply-patch script, and creating a new release
@@ -86,10 +140,22 @@ Refer to [Writers' Toolkit, Write documentation](https://grafana.com/docs/writer

Once a PR is merged to the main branch, if there are any changes made to the `docs/sources` folder, the GitHub Action [`publish-technical-documentation.yml`](https://github.com/grafana/k6-docs/blob/main/.github/workflows/publish-technical-documentation.yml) will sync the changes with the grafana/website repository, and the changes will be deployed to production soon after.

### Upgrade a main release
## Create a new release
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

@olegbespalov this might be helpful for the release day, let me know if this section makes sense. 🙇

Copy link
Member

@jdbaldry jdbaldry left a comment

Choose a reason for hiding this comment

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

LGTM

@heitortsergent heitortsergent merged commit ce67136 into main Dec 6, 2023
5 checks passed
@heitortsergent heitortsergent deleted the chore/readme-contributing-updates branch December 6, 2023 16:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants