This is an automated email from the ASF dual-hosted git repository.
nealsun pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/helix.git
The following commit(s) were added to refs/heads/master by this push:
new 59bdda6c5 Add optional helix-front PR template
59bdda6c5 is described below
commit 59bdda6c5ddfeb658dd35fd44a2e9de5a227de2f
Author: Micah Stubbs <[email protected]>
AuthorDate: Fri Sep 23 14:13:15 2022 -0700
Add optional helix-front PR template
Create PULL_REQUEST_TEMPLATE dir
to support multiple PR templates.
---
.github/PULL_REQUEST_TEMPLATE/helix_front.md | 39 ++++++++++++++++++++++
.../pull_request_template.md | 0
.github/workflows/helix-front.yml | 20 +++++++++++
3 files changed, 59 insertions(+)
diff --git a/.github/PULL_REQUEST_TEMPLATE/helix_front.md
b/.github/PULL_REQUEST_TEMPLATE/helix_front.md
new file mode 100644
index 000000000..98a536fb3
--- /dev/null
+++ b/.github/PULL_REQUEST_TEMPLATE/helix_front.md
@@ -0,0 +1,39 @@
+### Description
+
+<!-- Write a concise description: "what?, why?, how?" and then add some
details about this PR, including screenshots of any UI changes -->
+
+<!-- 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
-->
+
+This PR
+
+Fix #
+
+### Tests
+
+New unit or integration tests:
+
+<details>
+
+### Code Style
+
+<!-- Ensure the PR diff has been formatted using
[Prettier](https://prettier.io) -->
+
+Formatted using [Prettier](https://prettier.io)
+
+### Commits
+
+- My commits all reference appropriate Apache Helix GitHub issues in their
subject lines. In addition, my commits follow the guidelines from "[How to
write a good git commit message](http://chris.beams.io/posts/git-commit/)"
+
+### 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 -->
+
+</details>
diff --git a/.github/pull_request_template.md
b/.github/PULL_REQUEST_TEMPLATE/pull_request_template.md
similarity index 100%
rename from .github/pull_request_template.md
rename to .github/PULL_REQUEST_TEMPLATE/pull_request_template.md
diff --git a/.github/workflows/helix-front.yml
b/.github/workflows/helix-front.yml
new file mode 100644
index 000000000..b5851b079
--- /dev/null
+++ b/.github/workflows/helix-front.yml
@@ -0,0 +1,20 @@
+name: helix-front
+on:
+ pull_request:
+ branches: [ master ]
+ paths:
+ - 'helix-front/**'
+
+jobs:
+ test:
+ name: Test helix-front
+ runs-on: ubuntu-latest
+ steps:
+ - uses: actions/checkout@v1
+ - uses: bahmutov/npm-install@v1
+ with:
+ working-directory: helix-front
+
+ - name: helix-front format:check
+ run: cd helix-front && npm run format:check
+ working-directory: helix-front
