search

operate-first / common

Git Hub organization configuration
GNU General Public License v3.0
6 stars 64 forks source link

Prow not applying changes from PR that got merged #101

Closed Gregory-Pereira closed 2 years ago

Gregory-Pereira commented 2 years ago

Describe the bug I created a PR changing the github-config.yaml file to grant permissions, but the changes did not get applied by Prow. I went to take a look at the logs and its saying that "Configuration failed: failed to configure operate-first repo... The branch main was not found. Please push that ref first or create it via the Git Data API"

To Reproduce Steps to reproduce the behavior:

  1. Go to Operate-first/common
  2. Create a PR changing the permissions or any label, or simply view the Prow logs for an existing PR
  3. Check the logs for the peribolos check
  4. See error

Expected behavior The ability to have permissions granted view Prow.

/cc @harshad16

sesheta commented 2 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

harshad16 commented 2 years ago

@Gregory-Pereira is this still happening if it is not , please close this

sesheta commented 2 years ago

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

Gregory-Pereira commented 2 years ago

Seeing as #145 's checks went through I am going to assume this is no longer an issue. Temporarily closing this issue, but will re-open if new evidence comes to light.