[
https://issues.apache.org/jira/browse/BEAM-7985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16908377#comment-16908377
]
Mark Liu commented on BEAM-7985:
--------------------------------
The instruction points to query parameter `template` in
https://help.github.com/en/articles/about-automation-for-issues-and-pull-requests-with-query-parameters.
However, I didn't find a way to auto-populate it when creating a website PR,
which means contributors need to know the template name and manually add
`?template=xxx` to URL. This is not an ideal solution since not all
contributors know what template to use and can do it manually. It's not
scalable either if more customized templates are added.
> Separate PR template for website changes only
> ---------------------------------------------
>
> Key: BEAM-7985
> URL: https://issues.apache.org/jira/browse/BEAM-7985
> Project: Beam
> Issue Type: Wish
> Components: website
> Reporter: Mark Liu
> Priority: Major
>
> Currently we are using single template
> https://github.com/apache/beam/blob/master/.github/PULL_REQUEST_TEMPLATE.md
> for any new PR. However, those postcommit tables are not needed for website
> changes. And we would like to include staged link which is automatically
> created by Jenkins beam_PreCommit_Website_Stage_GCS_Commit (see details
> [here|https://cwiki.apache.org/confluence/display/BEAM/Website+Tips]). It
> would be much easier for people to review and find problem.
> So we can use separate PR template to do it. The instruction of multiple
> template can be found in
> https://help.github.com/en/articles/creating-a-pull-request-template-for-your-repository
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
