Update semconvgen.yml workflow to run on feature/* branches

[arminru]

This should allow @lmolkova's changes from #243 to be published under a specific tag on Docker Hub.

cc @open-telemetry/specs-semconv-maintainers

[Oberon00]

feature/ is a common prefix for a PR branch, should we not use a different prefix, like prerelease/ or something?

[arminru]

@Oberon00 that's the intent actually - we'd only have new features which we'd want to offer as a pre-release in such branches in this repo here. Any personal feature/ branch coming in from a fork (towards main or feature/ in here) should not be picked up by this workflow.

[jack-berg]

Hi - left a comment on #243 but figured I'd leave one here for more visibility.

The java SIG is looking to use the features of #243 in this PR. Couple of questions:

• Is there a timetable for publishing a docker image for the feature branch?
• Once a docker image is available, is it safe to use it to publish generated code using it? Not looking to publish stable artifacts, but essentially hoping that the new features of Support codegen by namespace #243 aren't going to go away. 🙂

[lmolkova]

Thanks!

[arminru]

@jack-berg

Is there a timetable for publishing a docker image for the feature branch?

We were only waiting for this PR to merged and it looks like it worked 🙂

https://hub.docker.com/r/otel/semconvgen/tags --> otel/semconvgen:feature-codegen-by-namespace

Once a docker image is available, is it safe to use it to publish generated code using it? Not looking to publish stable artifacts, but essentially hoping that the new features of #243 aren't going to go away. 🙂

You should be fine pointing at :feature-codegen-by-namespace for now but at some point we will want to merge this to main and then we'd also remove the feature branch and image.
This would then likely break your build in Java semconv but it should be a quick fix pointing it back at :latest.

[jack-berg]

Thanks so much!