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

feat: tag @amirmehrkar in PR/raise issue #16

Merged
merged 5 commits into from
Dec 3, 2021
Merged

feat: tag @amirmehrkar in PR/raise issue #16

merged 5 commits into from
Dec 3, 2021

Conversation

Jongmassey
Copy link
Contributor

No description provided.

@Jongmassey Jongmassey marked this pull request as ready for review December 1, 2021 14:51
action.sh Outdated Show resolved Hide resolved
@StevenMaude
Copy link

@Jongmassey: since you've requested review from @bloodearnest, I'll leave this as not yet approved.

@bloodearnest
Copy link
Member

We can create a Github team. @data-access-alerts maybe? Add Amir and Jon in at first?

@Jongmassey
Copy link
Contributor Author

That seems like a great idea

@Jongmassey
Copy link
Contributor Author

@opensafely-core/data-access would appear to be the name, not @Data-access

@Jongmassey
Copy link
Contributor Author

Interesting behaviour here is that I can't tag the team outside of the opensafely-core organisation. If the team is made within the opensafely org that may suffice, but what about if people have repositories in their own organisation? (is that supported with job server?)

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

Successfully merging this pull request may close these issues.

3 participants