[
https://issues.apache.org/jira/browse/NIFI-15794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18070877#comment-18070877
]
ASF subversion and git services commented on NIFI-15794:
--------------------------------------------------------
Commit 3e12ab9d51a40a194b2af13d1e9020c1e92002ad in nifi's branch
refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=3e12ab9d51a ]
NIFI-15794 Add Validation Steps to GitHub Build Workflow (#11103)
> Add Validation Steps to GitHub Build Workflow
> ---------------------------------------------
>
> Key: NIFI-15794
> URL: https://issues.apache.org/jira/browse/NIFI-15794
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Tools and Build
> Reporter: David Handermann
> Assignee: David Handermann
> Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> The GitHub Pull Request Template includes several steps required for
> validating whether the Pull Request meets Tracking requirements, including
> standardized references to a Jira issue in the Pull Request Title and commit
> messages. These Tracking requirements should be incorporated into a GitHub
> workflow that runs the checks, and adds a label to the Pull Request
> indicating valid or invalid status.
> The checks should align to the Pull Request Template, providing clear failure
> messages. Automatic Pull Request labeling could also provide the foundation
> for future improvements, such as automated closure after a shorter window,
> indicating requirements for reopening.
> These checks should be a requirement for running subsequent build jobs to
> avoid consuming unnecessary resources. This is also an opportunity to rename
> {{ci-workflow}} to something like {{{}build{}}}, aligning with more focused
> workflow names.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
