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

Creating New Merged Team #1122

Closed
1 task done
amejiamesinas opened this issue Jan 26, 2024 · 1 comment
Closed
1 task done

Creating New Merged Team #1122

amejiamesinas opened this issue Jan 26, 2024 · 1 comment
Assignees

Comments

@amejiamesinas
Copy link
Member

amejiamesinas commented Jan 26, 2024

Overview

During Org Meeting, ask Bonnie about creating merged team.

Action Items

  • Connect with Bonnie, add Sydney as Maintainer to new merged team

Resources/Notes

https://github.com/orgs/hackforla/teams/expunge-assist-merge/members

@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Jan 26, 2024

@sydneywalcoff I created a Merge team https://github.com/orgs/hackforla/teams/expunge-assist-merge/members

Here are the settings in the website repo under Settings > Branches to use as an example

screenshot

screencapture-github-hackforla-website-settings-branch-protection-rules-21239485-2024-01-26-13_23_05

I am excited to hear that you're planning to use some of the automations from the website team... with the following caveats

  1. we are in the process of refactoring all of them, so that they use a common variable file. And all labels will go into this variable file, so that if we change the name slightly, we don't have to figure out which GHA has to be edited, we can edit directly in the variable file. See this issue for more details Create JSON file and related functionality to support replacement of hard-coded issue labels website#5205
  2. We actually planned on taking the automations from website team and turning them into org wide automations. And this would be taken on after we revise all the GHAs on the website team. I would prefer if we make them global, and then you deploy them on expunge-assist. But that would involve waiting until the website team finishes their refactor, and then you becoming the lead of the migration to org wide (see currently proposal GitHub Actions Migration Process Proposal automate-the-org#10), which I would be happy to supply as many developers as you need to do whatever issues you create.

Let's have a meeting. I am sending you a link via Slack to make a 1-on-1 meeting with me, and I will invite Roslyn (the current website dev lead) to it.

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

No branches or pull requests

3 participants