Articles on: Integrations

Feedbucket and Github integration

Feedbucket can deeply integrate with Github. That means that your team should be able to manage all feedback inside of Github instead of in the Feedbucket Admin.


Install the Github integration on your Feedbucket project


  1. Go to your project and then click the tab Integrations.
  2. On the integrations page click the button Connect next to Github as show in the image below.

  1. If this is the first time you are connecting Feedbucket and Github you will be redirected to Github where you have to allow Feedbucket. Once the connection between Feedbucket and Github has been established you will be redirected back to Feedbucket.

  1. You will now see a green bar on the Github integration that indicates that the connection is made. The settings should have opened automatically but in case it doesn't, click on the Settings button to start configuring the Github connection for this project.



Configure the Github integration to your needs


Most often, you will create one Feedbucket project per client website you are building. That way you can connect each project to a specific repository inside of Github as well. It's up to you how you want to configure it.


After you connect you should see the configuration pop-up. If you don't, just click on the Open Settings button.


  1. Select the Repository. This is where Feedbucket will create issues on new feedback.
NOTE! In order for us to create webhooks, you need to have admin permissions on repo or be a repository owner


  1. (Optional) Select labels to set on the issue that Feedbucket creates.





How to use the Github integration


Once you have configured everything as you wish, below is how the integration should behave.


When new feedback is created


Whenever a new piece of feedback is created in Feedbucket, a issue will be created in Github. This issue will be placed in the repository that you selected in step #1 above. If you set any labels as in step #2, the issue will automatically have these labels. The issue will automatically have all of the technical details that Feedbucket collected like the session information of the reporter, the screenshot/recording etc.


Note that the issue created in Github will be created by the account that you configured Feedbucket and Github with in step #3 of the Installation above.



When a new comment is created on feedback


A piece of feedback can have lots of comments as a thread to communicate and collaborate. When a new comment is created on a piece of feedback that has been created in Github by Feedbucket, that comment will also be created in Github under the correct issue. That way, all comments that happens in Feedbucket will automatically be pushed to Github as well.


Comments created in Feedbucket will automatically be attached to the Github issue


As you can see in the image the real power lies in the two-way communication here. If your team needs to ask a follow-up question that can be done without leaving Github. All you have to do is to add a new comment that starts with @feedbucket and it will automatically be pushed over to Feedbucket and notify the client of this new comment from you. Regular comments submitted without the prefix of feedbucket will not sync over so you can continue to keep your internal conversations flowing in Github.


When using the at (@) symbol in Github it will think you want to mention someone inside Github. You should just write the @feedbucket as regular text and not click in the mention drop down.



When the feedback is resolved


If the feedback gets resolved from Feedbucket, the issue will automatically be closed in Github.


Again, there is a 2-way integration here as well. If your team has completed the feedback they can close the issue inside of Github and it will automatically resolve in Feedbucket. This way your team can manage all aspects of the feedback without leaving Github.



When the feedback gets re-opened


If the feedback gets re-opened from Feedbucket we will open the issue again.


We have 2-way integration here as well. If you re-open the issue inside Github it will be re-opened in Feedbucket as well.



FAQ


What permissions are required to integrate with Github?

You need to have admin permissions on the repository or be a repository owner. The reason why is for us to be able to create webhooks so the 2-way communication works.

Updated on: 12/02/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!