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

Ci/CD Automatic conflict resolving does not work #1113

Open
VitalyGushin opened this issue May 16, 2024 · 4 comments
Open

Ci/CD Automatic conflict resolving does not work #1113

VitalyGushin opened this issue May 16, 2024 · 4 comments
Assignees
Labels
bug Something isn't working

Comments

@VitalyGushin
Copy link

#1111
#1112

@VitalyGushin VitalyGushin converted this from a draft issue May 16, 2024
@VitalyGushin VitalyGushin moved this to Todo in Release v1.14.0 May 16, 2024
@denis-tingaikin denis-tingaikin changed the title Automatic conflict resolving does not work Ci/CD Automatic conflict resolving does not work May 16, 2024
@denis-tingaikin denis-tingaikin added the bug Something isn't working label May 16, 2024
@NikitaSkrynnik
Copy link
Contributor

NikitaSkrynnik commented May 17, 2024

Another Issue

When we have conflicts in PRs ci workflow doesn't start. We should check and resolve any conflicts on PR creation. Steps:

  1. Copy check-mergeability and resolve-conflicts jobs and put them after this job
  2. Remove this condition from the copied check-mergeability job
  3. Add needs: [auto-pull-request] into conditions of the copied check-mergeability job

@Ex4amp1e
Copy link
Contributor

@Ex4amp1e Ex4amp1e removed their assignment May 28, 2024
@denis-tingaikin denis-tingaikin moved this from Under review to Moved to next release in Release v1.14.0 Sep 24, 2024
@denis-tingaikin
Copy link
Member

Latest incidents: #1209, #1211

@LionelJouin
Copy link
Member

I checked the CI: https://github.com/networkservicemesh/.github/blob/main/.github/workflows/check-mergeability.yaml
The caller of this job is ran on push event: https://github.com/networkservicemesh/cmd-forwarder-vpp/blob/main/.github/workflows/pr-for-updates.yaml

This means that github.event.workflow_run.head_branch will be null.

A way to avoid that would be to check if github.event.workflow_run is null and use something like github.event.push.head_commit instead (https://docs.github.com/en/webhooks/webhook-events-and-payloads#push)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Moved to next release
Status: No status
Development

No branches or pull requests

5 participants