Integration for Commits

[github]

Integration for Commits

[primetheus]

@piyushchordia-fis this integration works by Pull Requests. It will validate all commits in the pull request, but it won't run just on a commit.

1. Enable branch protection on your main, master, feature**/**/* and release**/**/*
2. Open a pull request to the desired branch (with branch protection you cannot push directly to these branches without a pull request)
3. The Rally integration will check all commit messages in that pull request and block the approval until each has a user story

Does that help?

[piyushchordia-fis]

Thanks Jared for the response.
Are there any plans to integrate Commits also in future?

[primetheus]

@piyushchordia-fis what would be the desired functionality for commits? It will validate all commits in a pull request, but GitHub doesn't have any actions it takes on commits outside of a pull request. Are you wanting to block commits that don't have a valid user story in them? The current workflow for this app:

1. Create branch
2. Commit changes locally
3. Push changes to branch in GitHub
4. Open pull request
5. App validates all commits
   • if any commit is missing a user story, defect, etc, block the pull request
   • if all commits are validated, allow this check to pass

In this scenario all commits are checked for all branches as they go through the flow. You could conceivably create a pre-receive hook that checks commits as they come it, but I wouldn't recommend that for a few reasons:

• pre-receive hooks only work on GHES (self-hosted, not github.com)
• pre-receive hooks have a non-configurable timeout of 5 seconds
• pre-receive hooks that depend on external systems often become blockers for productivity

[piyushchordia-fis]

Thanks for sharing the details
I Agree, there wont be a commit without a PR .
But once we do commit in a branch there will be CI build triggered followed by auto deployment and testing.
In Rally there is an option in ChangeSet i.e Builds which will show Jenkins/CI Tool URL for that commit and also if there are Test cases if ran will be available in "Test Run" Tab.

This will be a end to end lifecycle of code committed on GITHUB.

[primetheus]

@piyushchordia-fis in this case there will be a connection in Rally under the Connections tab which links back to this pull request. There is a ChangeSet API that we can leverage to do something there, but I'm not quite sure how to tie in this bot with CI very easily from a workflow perspective. With Actions we could probably hook in and make this integration a part of the workflow, but with Jenkins, Travis, Circle, etc, we would need to to tailor this to each environment and have a dynamic way of hosting the app.

[primetheus]

Closing this one. @piyushchordia-fis if more clarity is needed please feel free to re-open this issue 🙇🏽