Repository navigation
Docs: Close the issue after the develop merge - #14
Merged
Merged
Conversation
Closes #N only fires on merges into main; feature pull requests merge into develop, so the issue has to be closed explicitly.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
GitHub closes an issue from
Closes #Nonly when the PR merges into the default branch (main). Our feature PRs merge into develop, so the issue stayed open (python-multiplatform #12, Gemstone #58). AGENTS.md section 4 now says to close the issue withgh issue closeafter the develop merge.