You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 24, 2022. It is now read-only.
Pivotal provides the GITBOT service to synchronize issues and pull requests made against public GitHub repos with private Pivotal Tracker projects our engineering team use to manage them.
If you are a Pivotal employee, you can configure GITBOT to sync your GitHub repo to your Pivotal Tracker project with a pull request.
Steps:
Fork this repo: cfgitbot-config (an ask+cf@ ticket is the fastest way to get read access if you get a 404)
Add your project to config-production.yml file
Submit a PR
If you are not a pivotal employee, you can request that [email protected] set up the integration for you.
You might also be interested in configuring GitHub's Service Hook for Tracker on your repo so you can link your commits to Tracker stories. You can do this yourself by following the directions at:
Pivotal provides the GITBOT service to synchronize issues and pull requests made against public GitHub repos with private Pivotal Tracker projects our engineering team use to manage them.
If you are a Pivotal employee, you can configure GITBOT to sync your GitHub repo to your Pivotal Tracker project with a pull request.
Steps:
If you are not a pivotal employee, you can request that [email protected] set up the integration for you.
You might also be interested in configuring GitHub's Service Hook for Tracker on your repo so you can link your commits to Tracker stories. You can do this yourself by following the directions at:
https://www.pivotaltracker.com/blog/guide-githubs-service-hook-tracker/
If you do not use Pivotal Tracker to manage this GitHub repo, please feel free to close this issue without taking any action.
If there are any questions, please reach out to [email protected].
The text was updated successfully, but these errors were encountered: