Additionally consider PR merge commits when filtering PRs #40
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds the ability for chronicle to consider PR merge commits relative to the release branch as a primary source of evidence for what to include or exclude from a release.
Take for example the following state:
2023-01-17 19:27:24 UTC
(relative to GitHub servers), but the tag was done locally at2023-01-17 19:27:23 UTC
. Note, they are 1 second off, implying that there is drift from the local time and GitHub's servers.This PR takes PR merge commits into consideration:
Note the
[0001] TRACE PR #45 filtered out: has merge commit outside of valid set 66b2b06b9a2eb9647acf55e8536c4d49e5d66066
, upon attempting to release v0.3.0.This PR additionally fully implements the
anchore/go-logger
interface.