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

Set up GitHub PR notifications for slack channel #1665

Open
bberhane opened this issue Feb 2, 2024 · 8 comments
Open

Set up GitHub PR notifications for slack channel #1665

bberhane opened this issue Feb 2, 2024 · 8 comments
Assignees
Labels
Complexity: Small draft Feature: automations Tickets relating to the set up or implementation of repository automations ready for dev lead ready for developer lead to review the issue Role: DevOps infrastructure, CI or related work size: 0.25pt Can be done in 1.5 hours

Comments

@bberhane
Copy link
Member

bberhane commented Feb 2, 2024

Overview

We need to set up GitHub PR notifications for Slack so that team members can stay up to date on new tickets and progress of existing tickets.

Action Items

Resources/Instructions

Page to do the setup for the 311 team https://github.com/orgs/hackforla/teams/311-data-write/settings/reminders/

Example of how our slack app is set up to deliver GitHub PR info to Slack channel

screenshot

screencapture-github-orgs-hackforla-teams-website-write-settings-reminders-30588-2024-02-01-19_37_34

Example from our Slack channel #hfla-site-pr

screenshot

image

@ExperimentsInHonesty ExperimentsInHonesty changed the title Test issue Setup GitHub PR notifications to slack channel Feb 2, 2024
@bberhane bberhane changed the title Setup GitHub PR notifications to slack channel Set up GitHub PR notifications for slack channel Feb 5, 2024
@bberhane bberhane added Role: DevOps infrastructure, CI or related work size: 0.25pt Can be done in 1.5 hours ready for product ready for a PM to review or assess and removed Milestone: Missing Role: Missing size: Missing draft labels Feb 5, 2024
@ryanfchase ryanfchase added ready for prioritization ready for PMs to consider for prioritized backlog and removed ready for prioritization ready for PMs to consider for prioritized backlog labels Feb 5, 2024
@ryanfchase
Copy link
Member

@bberhane thanks for setting up the ticket! I've prioritized it and cleared you from assignees since now it's ready to be picked up.

@dantor09 dantor09 self-assigned this Feb 11, 2024
@dantor09
Copy link
Member

  • Availability: Thursday 2/15 after 7 PM Saturday 2/17 after 1 PM Sunday 2/18 after 3 PM
  • ETA: Thursday 2/15 or Saturday 2/17

@ryanfchase
Copy link
Member

ryanfchase commented Feb 14, 2024

@dantor09 I noticed some activity from GitHub on #311-data slack channel. Can you make sure that the PR notifications happen on #311-data-engineering?

@dantor09
Copy link
Member

Hi @ryanfchase I am trying to remove the bot from #311-data but I do not see the remove button under the #311-data channel
Screenshot 2024-02-14 at 19 00 57

@dantor09
Copy link
Member

@ryanfchase The link to this page on github is returning a 404 http response for me. https://github.com/orgs/hackforla/teams/311-data-write/settings/reminders/
I think this may be a permissions barrier. I am trying to set up the reminders every day at 9 AM for the #311-data-engineering channel on slack.

I am using this documentation to set the reminders up:
https://docs.github.com/en/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team#creating-a-scheduled-reminder-for-a-team
Once I get to the teams page, I do not have the option for "settings" to set up reminder.

@ryanfchase
Copy link
Member

I think @dantor09 was able to provide instructions for a PM (with proper credentials) to set up the slack channel reminders. Moving this to icebox until we decide we ought to do this.

@ryanfchase ryanfchase added the Feature: automations Tickets relating to the set up or implementation of repository automations label Sep 9, 2024
@ryanfchase ryanfchase added Dependency An issue that includes dependencies and removed Feature: Missing labels Sep 9, 2024
@ryanfchase ryanfchase moved this from In progress to Icebox (on hold) in P: 311: Project Board Sep 9, 2024
@ExperimentsInHonesty ExperimentsInHonesty added ready for dev lead ready for developer lead to review the issue draft labels Feb 7, 2025
@ExperimentsInHonesty ExperimentsInHonesty moved this from Icebox (on hold) to Questions in P: 311: Project Board Feb 7, 2025
@ExperimentsInHonesty
Copy link
Member

Would the dev team benefit from this? Check the HfLA Slack channel #hfla-site-pr to see what it would like.

@ryanfchase ryanfchase removed the Dependency An issue that includes dependencies label Feb 9, 2025
@ryanfchase
Copy link
Member

After reviewing #hfla-site and #hfla-site-pr, I don't feel that it would be helpful for our smaller team.

  • our team used to assign one member each week to do PR announcements
  • I could also do the PR announcements

But I will add this to an upcoming Dev meeting agenda just so that each member can have their say.

@cottonchristopher cottonchristopher added the Complexity: Missing This ticket needs a complexity (good first issue, small, medium, or large) label Feb 9, 2025
@ryanfchase ryanfchase added Complexity: Small on agenda: dev this ticket will be discussed at the upcoming dev meeting and removed Complexity: Missing This ticket needs a complexity (good first issue, small, medium, or large) labels Feb 10, 2025
@ExperimentsInHonesty ExperimentsInHonesty moved this from Questions to New Issue Approval in P: 311: Project Board Feb 15, 2025
@ryanfchase ryanfchase self-assigned this Feb 20, 2025
@ryanfchase ryanfchase removed ready for product ready for a PM to review or assess on agenda: dev this ticket will be discussed at the upcoming dev meeting labels Feb 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Small draft Feature: automations Tickets relating to the set up or implementation of repository automations ready for dev lead ready for developer lead to review the issue Role: DevOps infrastructure, CI or related work size: 0.25pt Can be done in 1.5 hours
Projects
Status: New Issue Approval
Development

No branches or pull requests

5 participants