Skip to content
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

Remove some steps from resolve-conflicts workflow #73

Conversation

NikitaSkrynnik
Copy link
Contributor

@NikitaSkrynnik NikitaSkrynnik commented Apr 22, 2024

Description

Remove an unneeded condition from resolve-conflict workflow. This condition checks if the workflow has already tried to resolve conflicts in previous 10 commits. The problem is if a PR has less then 10 commits then the condition also checks main branch. If there are resolved conflicts from other PRs in the main branch they will be taken into account too. Therefore, sometimes this workflow doesn't work because of other PRs.

Issue

networkservicemesh/cmd-forwarder-vpp#1102

Copy link
Member

@denis-tingaikin denis-tingaikin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As I recall, we decided to apply another kind of fix for the issue.

@Ex4amp1e Could you remind?

@NikitaSkrynnik
Copy link
Contributor Author

I think we need to use something like this:

git log --oneline main..HEAD

It will show all the commits in the current branch and won't add any commits from the main branch

@NikitaSkrynnik
Copy link
Contributor Author

NikitaSkrynnik commented Aug 9, 2024

Created an issue where a better solution for this problem is described: #84

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants