Skip to content

Update CHANGELOG.md#65

Merged
andybeet merged 3 commits into
devfrom
hmorzaria-patch-1
Jun 8, 2026
Merged

Update CHANGELOG.md#65
andybeet merged 3 commits into
devfrom
hmorzaria-patch-1

Conversation

@hmorzaria

@hmorzaria hmorzaria commented May 28, 2026

Copy link
Copy Markdown
Collaborator

Added commit number for latest release

Your commits explain the who, what, where and when of these changes. Your code shows the how. You do not need to reiterate this. This PR should complete the big picture by telling the why.

Justification

Added commit number for latest push to main

Describe the big picture of your changes here to communicate to the reviewers why they should accept this pull request.
Please describe the importance/impact of the problem and a description of how the changes in this pull request will address, resolve or improve the problem.

If it fixes a bug or resolves a feature request, be sure to link to the issue below.

Types of changes

What types of changes does your code introduce? Put an x in the boxes that apply

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Other change (if none of the other choices apply)

Change to documentation

Further comments

If this is a New Feature, Breaking change, or a bug fix, the Atlantis Manual will need to be updated to reflect these changes.
Now would be a good time to create an issue in the Atlantis Manual repo and begin documenting your changes.

  • I've created an issue
  • This is NA

Reviewer instructions:

Assign at least 2 reviewers:

  • one of which should be a maintainer,
  • the others should be familiar with the subject changes. Please add these under the assignees field

Please detail the process reviewers will need to follow to properly test these changes. It is especially helpful to identify the exact code needed to conduct a local build/review/test and to specify any aspects of the testing that may not be obvious.

hmorzaria added 2 commits May 27, 2026 20:05
Added commit number for latest release
@hmorzaria hmorzaria marked this pull request as draft May 28, 2026 03:29
@hmorzaria hmorzaria changed the base branch from main to dev May 28, 2026 03:30
@hmorzaria hmorzaria requested a review from andybeet May 28, 2026 03:30
@hmorzaria hmorzaria marked this pull request as ready for review May 28, 2026 03:32
@andybeet

Copy link
Copy Markdown
Collaborator

Do you think it is worth hyperlinking to these commits in the changelog? How is this typically implemented? I'm not familiar with it.

We might also want to think about removing the line about "adhering to semantic versioning" and come up with an alternative description of how we are doing the versioning

@andybeet andybeet left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Should we hyperlink the commit?

Comment thread CHANGELOG.md Outdated
Comment thread CHANGELOG.md
Added hyperlink to commit

Co-authored-by: Andy Beet <22455149+andybeet@users.noreply.github.com>
@hmorzaria hmorzaria requested a review from andybeet June 8, 2026 18:32
@andybeet andybeet merged commit 48ecdfe into dev Jun 8, 2026
1 check passed
@andybeet andybeet deleted the hmorzaria-patch-1 branch June 8, 2026 19:46
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.

2 participants