-
This is a problem I have encountered several times across different dotnet repositories. You see a pull request have been merged but you have no idea in which exact release it landed. The fastlane repository does this and it's awesome, see fastlane/fastlane#17611 (comment) for example. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
@mmitche has this been considered? |
Beta Was this translation helpful? Give feedback.
-
You can find the list of releases that the PR/commit is from in the github UI. For example, go to #40637 and click on the " jkotas merged commit 7d152b7". You can see list of all releases that the change is in: You are right that there is no way to get actively notified today that would be achieved by adding a comment. Adding comment to the PR once it is included in a release will result in a massive spam for the people actively working on the repo each time we snap a release that is likely to have bad side-effects like spam filters blocking all github email, etc. I can see that it may ok for smaller repos with lower traffic (dotnet/runtime has ~20x more PR traffic than fastlane from your example). |
Beta Was this translation helpful? Give feedback.
You can find the list of releases that the PR/commit is from in the github UI. For example, go to #40637 and click on the " jkotas merged commit 7d152b7". You can see list of all releases that the change is in:
You are right that there is no way to get actively notified today that would be achieved by adding a comment. Adding comment to the PR once it is included in a release will result in a massive spam for the people actively working on the repo each time we snap a release that is likely to have bad side-effects like spam filters blocking all github email, etc. I can see that it may ok for smaller repos with lower traffic (dotnet/runtime has ~20x more PR traffic than fastlane from you…