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

Update report_changelog.md #302

Merged
merged 3 commits into from
Oct 7, 2024
Merged

Conversation

johspaeth
Copy link
Contributor

Naming convention:

  • PRs for features that are in design should have the "proposal" label
  • PRs for features that haven't landed yet should have the "future" label
  • PRs for upcoming releases should have the "release" label
  • PRs with new documentation for existing features should have the "existing feature" label

Before requesting review:

  • Make sure there is a ticket in the DOC board in Jira
  • Make sure CI is passing
    • Spell check failure may require adding backticks around code or updating spelling_wordlist.txt
    • See README.md for information about style and markdown syntax
    • If the CI Details link gives a 404, you need to log in to readthedocs.com
  • Add link to generated documentation here
    • you can find this by following the read the docs link from the CI check
  • Ask for help in #documentation

Jira ticket: TODO
Link to generated documentation: TODO

@johspaeth johspaeth added the release documentation for an upcoming release label Oct 1, 2024
@urikirsh urikirsh merged commit e7bfbc2 into master Oct 7, 2024
2 checks passed
@urikirsh urikirsh deleted the johspaeth/rule_report_release2.4.1 branch October 7, 2024 20:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release documentation for an upcoming release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants