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

Arch-BOM PR review process updates #816

Closed
2 tasks done
robrap opened this issue Oct 2, 2024 · 6 comments
Closed
2 tasks done

Arch-BOM PR review process updates #816

robrap opened this issue Oct 2, 2024 · 6 comments

Comments

@robrap
Copy link
Contributor

robrap commented Oct 2, 2024

See note at top of https://2u-internal.atlassian.net/wiki/spaces/AT/pages/16387065/On-Call+Arch-BOM#PR-Triage%2FReview for updated links.

  • Ensure process for OSPRs is correct. (@robrap is working on this, but in the meantime, I'd assume it is.)
  • Improve and document process for non-OSPR arch-bom owned PRs.

Notes:

  • See the on-call doc for notes on how we might handled the non-OSPR arch-bom owned PRs.
@robrap robrap added this to Arch-BOM Oct 2, 2024
@robrap robrap converted this from a draft issue Oct 2, 2024
@robrap
Copy link
Contributor Author

robrap commented Oct 4, 2024

I DMed Michelle (sorry this link isn't public), but it is just so I can check back if I fail to hear back, or fail to update this ticket.

@robrap
Copy link
Contributor Author

robrap commented Oct 4, 2024

@dianakhuang: Maybe part of this should spin off as a separate arbi-bom ticket, unless you just discuss and update?

@github-project-automation github-project-automation bot moved this to Backlog in Arbi-BOM Oct 7, 2024
@dianakhuang
Copy link
Member

We are more concerned with the backlog of upgrade bot PRs that are piling up. We will probably also need to create a separate stream of work around upgrades (arbi-bom) vs. other reviews(arch-bom).

@robrap
Copy link
Contributor Author

robrap commented Oct 7, 2024

Regarding the OSPR topic, I am taking the following as confirmation that this part is complete.

Questions from Robert:

Here are some hopefully more clear questions/confirmations:

  1. The Contributions board is still where we should be looking for PRs that need our attention, correct?
  • I think yes, but some of the views we used to use were removed, so I am just checking.
  1. For new PRs, if they are against a repo my team owns, then you will add 2u-arch-bom as "Repo Owner / Owning Team".
  • Confirming that that is the current process.
  1. I had a question of the status we should pay attention to, but decided to watch for anything that is not "Done". The link I had provided in my initial question had some status buried in the filter, but we'll just watch all status for now.
  2. Lastly, I believe you have a process for edx-platform with CCs and the new views that is working well enough for you? Or put another way, you are not expecting anything special on this front from my team that we aren't doing, right?

Responses from Michelle P.:

  1. Yes, the Contributions board is still where you should look. We cleaned up the views when the teams changed, but you can absolutely add an "arch-bom" view.
  2. Yes - for new PRs, if they are against arch-bom, I will add 2u-arch-bom as "Repo Owner / Owning Team".
  3. Re: the statuses, yes, anything that's not "Done" would be great. Tim and I do our best to make sure OSPRs have statuses up-to-date, but it takes a week or two for me to comb through all the ones I'm watching, so sometimes there are status changes that happen before Tim and I get to it (e.g. something might be ready for review, but not in that status yet because we haven't gotten back to it yet).
  4. The edx-platform view is all we really have right now for CCs to see which OSPRs in that repo need review, and there's lots still needing a reviewer. Nothing specific that arch-bom needs to do, but if you or another arch-bom member are able to review anything that's there, please feel free to do so!

@robrap
Copy link
Contributor Author

robrap commented Oct 7, 2024

Unfortunately, we can only filter out one bot (based on author) at a time (e.g. -author:edx-requirements-bot). If I add two of these filters, github just drops one. An alternative is to add a bot label (which one of these bots uses) for all bot PRs, so we can filter in or out bots as needed.

@robrap
Copy link
Contributor Author

robrap commented Oct 11, 2024

@dianakhuang: I moved the arbi-bom bot process questions to the following issue. Feel free to update its text as you wish.

The rest of this I have taken care of, so I am going to mark this ticket closed.

@robrap robrap closed this as completed Oct 11, 2024
@github-project-automation github-project-automation bot moved this from Backlog to Done in Arbi-BOM Oct 11, 2024
@github-project-automation github-project-automation bot moved this from Ready For Development to Done in Arch-BOM Oct 11, 2024
@jristau1984 jristau1984 moved this from Done to Done - Long Term Storage in Arch-BOM Nov 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Status: Done - Long Term Storage
Development

No branches or pull requests

2 participants