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

Add Needed: replication label #3138

Merged
merged 1 commit into from
Dec 5, 2017
Merged

Conversation

RichardLitt
Copy link
Member

@RichardLitt RichardLitt commented Oct 2, 2017

This was brought up in #2775, and will be useful to add along with the bug label.

Once this has been merged, we can create the label accordingly.

Note: I mistakenly opened this PR automatically from my CLI with old text. I have since edited it. Sorry about that.

This was broght up in #2775, and will be useful to add along with the `bug` label.

Once this has been merged, we can create the label accordingly.
@RichardLitt RichardLitt changed the title docs: repository audit Add Needed: replication label Oct 2, 2017
@agjohnson
Copy link
Contributor

Makes sense. There are probably a number of cases I've not responded to a bug because I didn't have time to replicate the issue.

I can push this out to all of our repos, I have this scripted. I'll leave this open until I've completed the push out.

@agjohnson agjohnson self-assigned this Oct 3, 2017
@Blendify
Copy link
Member

Poke

Copy link
Member

@humitos humitos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd say that this one is ready to merge. The label is already created in the repo

@ericholscher what do you think?

@ericholscher
Copy link
Member

LGTM!

@ericholscher ericholscher merged commit 5e98e15 into master Dec 5, 2017
@stsewd stsewd deleted the feat/add-needs-replication-label branch August 15, 2018 22:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants