Git Product home page Git Product logo

Comments (8)

danielrozenberg avatar danielrozenberg commented on May 24, 2024

That makes sense. I wonder if the PR approval model is the best way, or whether we should move to an explicit approval of the check using an action button (which is a relatively new feature for GitHub Apps, that's why it wasn't considered before)

wdyt?

from amp-github-apps.

jridgewell avatar jridgewell commented on May 24, 2024

I like being able to approve a PR with a general PR approval, though. Would this require me to hit a second button?

from amp-github-apps.

danielrozenberg avatar danielrozenberg commented on May 24, 2024

It would (from the PR you'd have to click the Details link on the check, and then the Approve link). So you prefer the current approach

from amp-github-apps.

danielrozenberg avatar danielrozenberg commented on May 24, 2024

Hmm... the problem with re-running the check to verify the approvals is that it can't tell these two scenarios apart:

  1. bundle-size approval is required → PR is approved → some error causes the approval not to be registered
  2. bundle-size approval is required → PR is approved → commit is pushed → bundle-size approval is required again

from amp-github-apps.

rsimha avatar rsimha commented on May 24, 2024

One advantage of separating general PR approval from size-increase approval is that a reviewer who happens to be a bundle-size owner a review a PR without inadvertently allowing the size increase to sneak through. I'll defer to @danielrozenberg's judgement on this, since he's more aware of the corner cases.

While on the topic of approvals, I'd like to make a case for #141, which proposes that we switch the size increase approvers from a hard-coded list to the runtime working group. WDYT?

from amp-github-apps.

jridgewell avatar jridgewell commented on May 24, 2024

Shouldn't it be checking the order of commits/approval?

from amp-github-apps.

danielrozenberg avatar danielrozenberg commented on May 24, 2024

I'll have to check whether the API supports that, but it does complicate the app's code 1,000× >__>

from amp-github-apps.

danielrozenberg avatar danielrozenberg commented on May 24, 2024

We discussed this offline in the infra team and came to agree that fixing this is not worth the effort, given the rarity of the root cause (GitHub API/webhook failures) - the easiest solution in those cases is to rebase the last commit or close/reopen the PR. I'm going to close this issue as a won't-fix

from amp-github-apps.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.