-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
create global workflow that informs PR author about merge conflicts #181
Comments
This issue has been automatically marked as stale because it has not had recent activity 😴 It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation. There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model. Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here. Thank you for your patience ❤️ |
Hey @derberg ,I would like to work on this issue. |
@sambhavgupta0705 please go ahead |
Hey @sambhavgupta0705 are you still working on this? |
No ,@chinma-yyy |
Hey @derberg , I would like to work on this issue. Should I go ahead? |
sure, please |
Yup, sorry for late reply was on a vacation lately ✌️ |
Reason/Context
Sometimes PRs get merge conflicts. No notifications tell the PR creator about it. This causes some PRs to hang for some time. It affects release branches the most
Description
We need workflow, that once it detects merge conflict on a PR, it posts a comment in PR and mentions the author. The comment should inform the author that there is a merge conflict (this will trigger notification).
It should not be annoying and duplicate comments, so we can inspire on #175 and:
Bonus:
Maybe some tips on what is the best way to solve the merge conflict 🤔 good and bad practices.
Super bonus:
Additional workflow that anyone can trigger by adding comments like /rebase or /solve_conflict (/sf) would trigger a workflow that tries to solve the conflict in an automated way. Something to explore
The text was updated successfully, but these errors were encountered: