micahstubbs opened a new pull request, #2216:
URL: https://github.com/apache/helix/pull/2216

   ### Description
   
   <!-- Write a concise description: "what?, why?, how?" and then add some 
details about this PR, including screenshots of any UI changes --> 
   
   This PR adds a `helix_front` PR template that can be used by appending the 
`&template=helix-front.md` to the GitHub PR create link. 
   
   For example, the link to create this PR and use the new `helix-front.md` PR 
template is:
   
   
`https://github.com/apache/helix/compare/master...micahstubbs:helix:2215/pr-template?expand=1&template=helix-front.md`
   
   You can read more about [creating PR Templates] 
(https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository)
 and [using query parameters to create a pull 
request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request)
 in the Github docs.
   
   <!-- ### Issue -->
   
   <!-- This PR fixes this Helix issue & includes the Helix issue in the PR 
description. Link your issue number here: You can write `Fix #123`.  See 
https://docs.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue
 --> 
   
   Fix #2215
   
   ### Tests
   
   Tooling change only. 
   
   <!-- List the names of new unit or integration tests -->
   
   ### Code Style
   
   <!-- Ensure the PR diff has been formatted using 
[Prettier](https://prettier.io) -->
   
   Formatted using [Prettier](https://prettier.io)
   
   <!-- ### Changes that Break Backward Compatibility (Optional)
   
   - [ ] My PR contains changes that break backward compatibility or previous 
assumptions for certain methods or API. They include: -->
   
   <!-- Consider including all behavior changes for public methods or API. Also 
include these changes in merge description so that other developers are aware 
of these changes. This allows them to make relevant code changes in feature 
branches accounting for the new method or API behavior. -->
   
   <!-- ### Documentation (Optional)
   
   - [ ] In case of new functionality, my PR adds documentation in the 
following wiki page: -->
   
   <!-- Link the GitHub wiki you added -->
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to