To connect GitHub, get your DailyBot GitHub's hook URL and then configure a new WebHook in your GitHub repository using this URL. Then every user should configure their GitHub username in their DailyBot account. Keep on reading
What are the steps?
- Go to the Integrations page > GitHub, then copy your own hook URL.
- Go to your GitHub repository, and then navigate to Settings > Webhooks.
- Add a new webhook, paste the URL just copied from DailyBot.
- Select the Content Type as application/json.
- Make sure the "Enable SSL verification" is turned on.
- Configure the Triggers: select "individual events", and select one or all of the following: Pushes, Pull requests, Issues. – if there is an event you want to track and it's not supported, please contact us and let us know.
Notice: GitHub admin permissions may be required to configure the webhook.
How does DailyBot match GitHub users with DailyBot users?
It is recommended that all your team members configure their own GitHub usernames on DailyBot's GitHub page. They should access the Integrations page > GitHub, and then set the username.
If the username is not defined, DailyBot will try to match users based on the full name or other webhook metadata, but it will not work everytime. If that information does not match, the GitHub event will be ignored and no activity will be tracked in DailyBot.
Activate the check-in activity tracking
The activity tracked can be included in any stand-up or check-in reports. Such activity will be seen in @DailyBot's chatbot reports (sent to channels or DMs) or on the web app reports.
To make sure the activity is displayed, enable the activity tracking for the check-ins where you want to have this behavior.
1. Go to the check-in settings
2. Click Sharing, and then activate the "Activity tracking" on the advanced options section
You should enable this option in every check-in where you want to see activity in the reports.
What activity is shown in the reports?
There will be a new column automatically added to the check-in responses and it will contain any activity that was logged in the period starting 24 hours previous to the check-in response, and until end of the day current response.
Article is closed for comments.