Code quality is everything. People often use branches or pull requests on GitHub for specific issues and features. If you close the pull request too quickly, without proper QA and testing - you risk a constant and increasing stream of bugs. With this awesome integration - you can create a custom process on Tallyfy (as a blueprint) and launch it every time a new pull request is created or closed on GitHub.
Get started for free—14 day trial of premium features and apps.
No coding required—automate any of 1,500+ apps in minutes.
Enterprise-level security—connect mission-critical apps.
Launch Tallyfy processes for new GitHub issues
One of the biggest problems in software development is poorly defined issues and acceptance criteria. If you make a GitHub issue without sufficient detail, it not only frustrates developers but the issue might not even be confirmed as reproducible. Every time a new issue is created in GitHub - launch a process on Tallyfy to: - Check the issue is actually reproducible - Add proper details to the issue such as screenshots, URL's or even screencasts - Define dependencies, tags, milestones, priority and much richer context to the issue If you prep an issue right, a developer can get a lot more productive (and can do that far more quickly).
Note - create your blueprint on Tallyfy first.
It's easy to connect GitHub + Tallyfy and requires absolutely zero coding experience—the only limit is your own imagination.
Triggered when a new issue is created.
Creates a new gist.
Triggers when your Github username is mentioned in a Commit, Comment, Issue or Pull Request.
Create a new pull request and merge it (optional).
Triggered when a new commit is created. Select your organization, repo and branch.
Update an existing issue.
Triggered when a new comment on a commit is created.
Creates a standalone task.
Triggered when a new watcher is added to a repo.
Mark process task complete.