Git Workflow Discussion

Here is what I tried to do to make the automatic ticket update seem reasonable from GitHub. It is based on what I've been able to find in the support forums and other online write-ups.

Unfortunately, I still don't seem to have it down to a flow yet. As the ticket itself did not update from 'New' to 'needs_ack'; perhaps there is a time delay, or perhaps I did something wrong. :(

Account Setup

• In lighthouse create an API token to be used with npp-community projects.

• In GitHub, went to the Admin page for my forked repository and enter the required Lighthouse service hook details.

Ticket Creation

• Create an issue in Lighthouse.

Branch Work

Github service hooks don't work for a new repository branch, so...

• git checkout LH-5/tf/nppcr-project-files-overhaul master

• git push origin LH-5/tf/nppcr-project-files-overhaul

• Since I have a local topic branch that I already know is based on master and cleanly merges with it:

git merge --log --no-ff tf/nppcr-project-files-overhaul

git commit --amend -s

• Place the Lighthouse ticket information between the end of the merge summary and the signature.

'[#5 Make project building a no-brainer. state:needs_ack]'

• git push thell-nppcr LH-5/tf/nppcr-project-files-overhaul

Confirmation

After pushing the LH-5 branch that has the ticket info in the merge commit...

• Visit Issue #5