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 changelog xsd to 4.16 #3259

Merged
merged 1 commit into from Sep 8, 2022
Merged

update changelog xsd to 4.16 #3259

merged 1 commit into from Sep 8, 2022

Conversation

suryaaki2
Copy link
Contributor

Impact

  • Bug fix (non-breaking change which fixes expected existing functionality)
  • Enhancement/New feature (adds functionality without impacting existing logic)
  • Breaking change (fix or feature that would cause existing functionality to change)

Description

A clear and concise description of the change being made.

  • Introduce what was/will be done in the title
    • Titles show in release notes and search results, so make them useful
    • Use verbs at the beginning of the title, such as "fix", "implement", "improve", "update", and "add"
    • Be specific about what was fixed or changed
    • Good Example: Fix the --should-snapshot-data CLI parameter to be preserved when the --data-output-directory property is not specified in the command.
    • Bad Example: Fixed --should-snapshot-data
  • If there is an existing issue this addresses, include "Fixes #XXXX" to auto-link the issue to this PR
  • If there is NOT an existing issue, consider creating one.
    • In general, issues describe wanted change from an end-user perspective and PRs describe the technical change.
    • If this change is very small and not worth splitting off an issue, include Steps To Reproduce, Expected Behavior, and Actual Behavior sections in this PR as you would have in the issue.
  • Describe what users need and how the fix will affect them
  • Describe how the code change addresses the problem
  • Ensure private information is redacted.

Things to be aware of

  • Describe the technical choices you made
  • Describe impacts on the codebase

Things to worry about

  • List any questions or concerns you have with the change
  • List unknowns you have

Additional Context

Add any other context about the problem here.

@github-actions
Copy link

github-actions bot commented Sep 8, 2022

Unit Test Results

  4 620 files  ±0    4 620 suites  ±0   36m 12s ⏱️ - 2m 30s
  4 620 tests ±0    4 405 ✔️ ±0     215 💤 ±0  0 ±0 
54 612 runs  ±0  49 592 ✔️ ±0  5 020 💤 ±0  0 ±0 

Results for commit 81d8332. ± Comparison against base commit 072f1a5.

♻️ This comment has been updated with latest results.

@suryaaki2 suryaaki2 merged commit 49a9cb3 into master Sep 8, 2022
@suryaaki2 suryaaki2 deleted the update-changelog-xsd-4.16 branch September 8, 2022 15:33
@suryaaki2 suryaaki2 restored the update-changelog-xsd-4.16 branch September 8, 2022 16:02
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

2 participants