Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How to enable smart commits on repository forks (GitHub)

My team contributes to a GitHub repository by committing and pushing to individual forks (one per developer). Pull requests are opened against the parent repository, with releases being cut from there as well. I've been working on getting Smart Commits enabled, and I've hit one final snag before I can share it with my team:

I've been testing the smart commit integration in two ways. The first, by cutting a new branch directly on the parent repository, pushing to it, and opening a PR. All smart commit data I've sent via this path have worked as expected, but unfortunately, this is not the workflow our team uses.

My second test involves cutting a new branch on my personal fork of the project, pushing commits to it, and then opening a PR against the parent repository. No actions taken in this path are reflected in JIRA (even after waiting the default 60 minutes, so I think I've debunked the invalid OAuth probability).

As a last-ditch effort, I'm currently going through the process of registering my own fork under the DVCS accounts, and having done that, I now see the commits made on that second test branch showing in my issue's Development section (slowly but surely).

As time ticks by, I'm realizing JIRA is going through the heavy process of synchronizing my fork, which will essentially RE-ASSESS every commit in the parent repository. As such, this is taking quite some time, and I haven't been able to fully verify my testing as the sync isn't complete. Nonetheless, this seems like things could get extremely expensive if I'm expected to really be registering one repository for every fork we have in our company.

So, my question is, am I overlooking the expected process here? Should the parent repository's integration with JIRA be enough to pick up on pushes in forks? I followed the steps mentioned here to create the needed webhooks on the parent repository, and I confirmed those webhooks synced to my fork, but it doesn't seem like things are getting picked up. Any advice?

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in DevOps

Step up your DevOps game webinar Q&A series - Questions answered!

  On October 21st, 2020 we hosted a webinar titled,   Step Up You DevOps Game with 4 Key Integrations for Jira and Bitbucket. We had a great showing and high engagement, but that meant th...

118 views 0 1
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you