Hellonext - GitHub integrations allow Product Management and Development teams to be in sync allowing Product managers to track feature development from the Hellonext dashboard!The progress can happen in parallel and your team can be kept in the loop by using simple setup and efficient auto push and sync rules. Let’s take a look at how this is done!<h2>Scope for Hellonext - GitHub integration</h2><pre><code>Read access to metadata
Read and write access to issues, repository hooks, and repository projects</code></pre><h1>Getting started</h1><ol>
<li>Start by navigating to your Hellonext Dashboard → Organization Settings → Integrations.</li>
<li>
Scroll down to GitHub → Click on Connect.

<img src="https://vault.featureos.app/uploads/attachment/upload/9b3009be9c60c2503389ec9c6e18c612.png">

<blockquote>Please make sure the admin who has access to all the required repositories (for your team) sets up the integration. This is to make sure the issues from all the necessary repositories show up in the search results and appropriate issue creation from Hellonext to GitHub.</blockquote>

</li>
<li>
Sign into your GitHub account and authorize Hellonext to access your GitHub organization. You can either choose to sync with all the repositories on your GitHub organization or select specific repositories that your teams predominantly work with!

<img src="https://vault.featureos.app/uploads/attachment/upload/0bebb18e54976efbadcc82f6dc49d21e.png">
<blockquote>Make sure you do not select forked repositories.</blockquote>
</li>
</ol>Once done you’ll be redirected to your Hellonext integrations page where you can also find the details about which GitHub organization is connected to your Hellonext organization and the user profile used for this setup. You’re all set to configure the rules for your integration flow!<h1>Configuring Automatic Push to GitHub</h1>You can enable Automatic Push to GitHub to push Hellonext posts as issues to GitHub and set the rules to trigger this automatic push. You can choose multiple Hellonext boards as a part of this trigger.<blockquote> Note that you cannot push issues to forked repositories!</blockquote><ol>
<li>
The initial rule you set for “Automatic Push to GitHub” is when you change the status of the posts to one of the available statuses in the dropdown, the respective posts will be pushed to GitHub.

<img src="https://vault.featureos.app/uploads/attachment/upload/1b16e285ab7ba186172bf7b3e46864e1.png">
</li>
<li>Push posts immediately after submitting - To automatically push posts to GitHub as soon as they are created on Hellonext - you must enable the check box “New posts in In Review status will automatically be sent to GitHub.”</li>
<li>
Post moderation enabled - To automatically push posts to GitHub as soon as they are approved in moderation, on Hellonext - you must enable the check box “Posts approved in In Review status will automatically be sent to GitHub.”

</li>
</ol><h1>Setting up rules for status sync</h1>You can set up simple sync rules to automate the post sync between Hellonext posts and GitHub issues or vice versa! - An efficient two-way status sync to keep your Product and Development teams in Sync.You can click on the + New Sync Rule button to start adding rules! There are 3 types of Sync rules you can set -<ul>
<li>When Any linked GitHub issue is changed to a Status, change linked Hellonext posts to the set Status and Notify / Do not Notify voters and subscribers.</li>
<li>When All linked GitHub issues are changed to a Status, change linked Hellonext posts to the set Status and Notify / Do not Notify voters and subscribers.</li>
<li>
When a Hellonext post is changed to a Status, change all linked GitHub issues to the set Status.

<img src="https://vault.featureos.app/uploads/attachment/upload/e07743e012b2bf08f7c98faf05c653a8.png">
</li>
<li>Click on the Add Rule button to save the set rule.</li>
<li>Click on Save to save the Sync configuration.</li>
<li>
You can also find the details about which GitHub Organization is connected to your Hellonext organization and the user profile used for this setup.

<img src="https://vault.featureos.app/uploads/attachment/upload/48a362a84a6969e69ad20c5a78adb845.png">
</li>
</ul><hr><h1>How the integration works</h1>Once the Integration setup is complete, you will see a Push to GitHub button within all your posts on Hellonext, on the right panel. Clicking on Push to GitHub will give you two options:<h2>1. Create a GitHub issue</h2><ul><li>
Please note that only one GitHub issue can be created from a Hellonext post.

<img src="https://vault.featureos.app/uploads/attachment/upload/14a647daffd2e5ac147e93a88e4e0a8a.png">
</li></ul><ul>
<li>
In the Create tab, you can modify the Title and Description of the issue, You can also choose the relevant Repository on GitHub that this issue push must be made to.

<img src="https://vault.featureos.app/uploads/attachment/upload/91fc1e2981df810b2ed23bc4419ece87.png">
</li>
<li>Click on Push to GitHub once done.</li>
<li>
The GitHub issue created from a Hellonext post will contain the post title as the issue title and the description as the first comment, added by the Hellonext Bot.

<img src="https://vault.featureos.app/uploads/attachment/upload/0dddfb66352fd33bdb3a95779001e61a.png">
</li>
<li>
The created issue on GitHub is also added as a link to the Hellonext post and vice versa on Hellonext, which can help in quick redirection when needed.

<img src="https://vault.featureos.app/uploads/attachment/upload/be489abb3edbd16767b9f75c5cf5e9d5.png">
</li>
</ul><h2 style="text-align: start">2. Link GitHub issues</h2><ul>
<li>You can link multiple GitHub issues to a single Hellonext post.</li>
<li>
Toggle to the Link tab and search for GitHub issues to link using the title or ID.

<img src="https://vault.featureos.app/uploads/attachment/upload/350cfe9d6bff352faee5744cc0835abc.png">
</li>
<li>
Click on the Link button to link a GitHub issue to the Hellonext post, from the search result.

<img src="https://vault.featureos.app/uploads/attachment/upload/7778f2cdd07e0b9485711c162d8ab513.png">
</li>
<li>
Once linked, the GitHub issue will also contain a link to the Hellonext post.

<img src="https://vault.featureos.app/uploads/attachment/upload/ac99889a234b54c8cdf24e945ffadb82.png">
</li>
</ul><h2>3. Unlink a GitHub issue from a Hellonext post</h2>You can unlink a GitHub issue from a Hellonext post by simply clicking on the Unlink icon that appears at the right corner of the linked issue.<img src="https://vault.featureos.app/uploads/attachment/upload/ea1bc47d1f85540d6950bcd795489ce6.png">Please note that once you Unlink, the respective GitHub issue will no longer be available on that Hellonext post. You can still find the issue on GitHub.<img src="https://vault.featureos.app/uploads/attachment/upload/cc3aefce3bab199ab9c3ef26175d4cf1.png"><h2>4. Disconnect Hellonext - GitHub Integration</h2>To disconnect the Hellonext - GitHub Integration, head to your Organization Settings on the left panel of your Hellonext Dashboard → toggle to the Integrations tab → click on Configure for GitHub → click on Disconnect at the bottom left corner of the popup modal.<img src="https://vault.featureos.app/uploads/attachment/upload/b61b5acab49587ac433da460c5ec6bb8.png"><h2>5. Change Repository access on GitHub</h2>If you’d like to change the repositories that you have given Hellonext access to, you can navigate to Settings on your GitHub profile → choose Applications over the left → click on Configure for Hellonext.<img src="https://vault.featureos.app/uploads/attachment/upload/216eec77b26bcbf77324984951185351.png">You can then modify the Repository access as needed and Save the changes.<img src="https://vault.featureos.app/uploads/attachment/upload/c4101961a72eb2eeae7be8d55f5b5139.png">Seems rather easy and simple to follow, doesn’t it? That’s because it is! Do feel free to<a target="_blank" rel="noopener noreferrer nofollow" href="https://hellonext.co/contact"> reach out to us</a> if any queries should arise! 😃🙌🏼

How can we help you?

Engineering tools

GitHub Integration