Skip to content

SAVED_REPLIES.md

Latest commit

 

History

History
75 lines (56 loc) · 5.15 KB

SAVED_REPLIES.md

File metadata and controls

75 lines (56 loc) · 5.15 KB

Fueled Saved Replies

In order to help reduce the time it takes to respond to open Issues and Pull Requests, we should leverage GitHub’s Saved Replies to help when we are continually responding in the same manner. The following are various Saved Replies that the Fueled team should use to respond to Issues and Pull Requests to ensure our community responses are similar and to minimize the amount of time crafting the same response to different requests.

Since GitHub currently does not allow us to have a repository-wide or organization-wide list of saved replies, these replies need to be maintained by individual team members. Since the replies can be modified in the future, all responses are versioned to simplify the process of keeping the replies up to date.

While these Saved Replies attempt to give you the ability to quickly reply to Issues and Pull Requests, they are not meant to be the exact response you should use every time. Consider customizing them to fit the context of the Issue or Pull Request contribution you are replying to. You will be best served by welcoming the contributor to the project (if its their first issue/PR), thanking them for their contribution, giving them context to your response (especially if you're closing their issue/PR), and noting next steps (e.g., issue milestoned for a specific release, open to them submitting a PR to resolve an issue, sending a PR to someone else to review).

You can add these saved replies to your personal GitHub account here.

Sources: 1, 2, 3, & 4.

Issue: already fixed (v1)

Thanks for filing this Issue!  Fortunately it is now obsolete due to changes in a recent release.  Please update to the most recent version to resolve the problem.

If you are still having problems after updating, then please provide additional details for us to try and replicate your issue.

Issue: don't understand (v1)

I'm sorry but I don't understand the problem you are reporting.  Would you please rephrase your issue so I can attempt to better understand it?

Issue: can't reproduce (v1)

Thanks for filing this Issue!  Unfortunately I cannot reproduce the problem following the instructions you provided.  We require that reported issues have reproduction steps that highlights the problem.

If the problem still exists for you, then please include any additional information on how to reproduce it.

Issue: behaving as expected (v1)

It appears this behaves as expected.  If you still feel there is an issue, please provide further details on your problem.

Issue: template missing (v1)

Thanks for filing this Issue!  Please note that we have Issue templates for [bug](https://github.com/fueled/REPONAME/blob/develop/.github/ISSUE_TEMPLATE/1-bug-report.md), [enhancement](https://github.com/fueled/REPONAME/blob/develop/.github/ISSUE_TEMPLATE/2-enhancement.md), and [question](https://github.com/fueled/REPONAME/blob/develop/.github/ISSUE_TEMPLATE/3-help.md) requests.  I would appreciate it if you could edit your Issue and add in the missing details.

Issue: PR please? (v1)

I would love your help on this Issue, would be happy to review a PR for it, and will attempt to provide any assistance you might need.

Issue or PR: duplicate (v1)

Thanks for filing this (issue, PR).  However this is a duplicate of an existing (issue, PR) #NUMBER, so I'm closing this but if you think this was in error then don't hesitate to comment.  Otherwise please subscribe to #NUMBER for future updates.

Issue or PR: close as inactive (v1)

I'm closing this issue due to inactivity, but please let me know if you're still having problems so I can try to help... thanks!

Issue or PR: send for help! (v1)

Thanks for filing this!  Unfortunately I’m uncertain on how to proceed here, so I’m pinging (@maintainer, @fueled/open-source-practice) for their input.

PR: merging and more (v1)

This looks perfect, so I'll merge it.  If you are looking for another challenge, then please take a look at our `help-wanted` list: https://github.com/fueled/REPONAME/labels/help-wanted.  Thanks!

PR: template missing (v1)

Thanks for filing this PR!  Please note that we have a [PR template](https://github.com/fueled/REPONAME/blob/develop/.github/PULL_REQUEST_TEMPLATE.md) that is required.  I would appreciate it if you could edit your PR and add in the missing details.

PR: missing related Issue (v1)

Thanks for filing this PR!  Please note that we require an Issue for each PR so that approach and other details can be discussed in the Issue while code review can happen in the PR.  I would appreciate it if you could [open an Issue](https://github.com/fueled/REPONAME/issues/new/choose) and link it to this PR for further discussion.