[CI] Next steps

[kumarabd]

Current Behavior

Currently, Nighthawk builds are being published to this repository for Nighthawk version v0.2. This is being done manually but invoking a GitHub Action trigger, more details about this can be found here - https://docs.google.com/document/d/1lHfMo4iIx2WXFZIspfHyxTsPR1T63_2IV5NUkgxoo0w/edit#heading=h.9c7u4vmlywzu

Desired Behavior

Given that we have the pipeline working for building and publishing binary as well as docker artefacts, we would want to have this automated with the Nighthawk repository. There are a several proposed ways to do this, we would want your attention on the same.

*** Proposal:
Trigger the Gihub Action in this repository from the nighthawk repository

It will be helpful to have insights in this regard @mum4k @oschaaf @leecalcote

---

Resources

https://docs.google.com/document/d/1lHfMo4iIx2WXFZIspfHyxTsPR1T63_2IV5NUkgxoo0w/edit#heading=h.9c7u4vmlywzu

---

Contributor Resources

• See the Contributing to getnighthawk.dev Website
• See the Project Site section of GetNighthawk project doc

[mum4k]

The proposal sounds good to me.

One thing we haven't been doing in the nighthawk repository is advancing the release version (tagging new releases). We can use this opportunity to change that and start regularly publishing new versions.

Can you share the specifics on how the action will get triggered from the nighthawk repository? Can we attach the trigger to the creation of new tags? That way we can control when the release happens, rather than releasing on every commit which might result in partial / incomplete functionality.

[Mohdcode]

is this issue in work progress?