You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, if a PR is rejected (i.e closed without merging) it shows up in the changelog. Since this is a change that does not active affect the code base, it feels like it should not be included in the changelog by default.
Granted we could also remove it from the milestone, but I believe it can also remain there for organization reasons, like knowing which release the PR had been intended for and finding more history on it.
The text was updated successfully, but these errors were encountered:
Currently when this happens I do what you suggested and remove it from the milestone. Not opposed to adding this though if the github API supports differentiating the data.
Right now, if a PR is rejected (i.e closed without merging) it shows up in the changelog. Since this is a change that does not active affect the code base, it feels like it should not be included in the changelog by default.
Granted we could also remove it from the milestone, but I believe it can also remain there for organization reasons, like knowing which release the PR had been intended for and finding more history on it.
The text was updated successfully, but these errors were encountered: