Collaborate?

[LongLiveCHIEF]

Hello!

I recently wrote https://github.com/marketplace/actions/tagging-strategy.

This action has a very similar purpose, but supports different features as yours.

Do you guys want to collaborate or potentially merge these two actions?

Collaboration to me would mean figuring out what the distinct scope/use-cases work best for each action, stating that use-case in README's, and then mentioning the other's actions in each README for when users find one but their use case matches the other.

Merging to me would be if both groups agree the scope and use case is the same, and both groups believe all features could exist in one action.

Interested in hearing your thoughts.

[coreybutler]

Apologies for the delay, I never saw the notice of this issue.

I'm not opposed to working with other folks, but I don't see anything in the tagging-strategy action that this one doesn't do. Feel free to point me in the right direction if I'm missing something.

[LongLiveCHIEF]

Your package detects tags and is designed to work well in a job matrix where there may be multiple dockerfiles (resulting in multiple tags).

Mine extrapolates new tags based on a tag itself, and assumes a single Dockerfile can be responsible for dozens of different tags.

Both are common patterns with docker today, and both are one half of the total pattern.