Hello, Another feature request today regarding the Github project configuration and Github commit tags. We have 4 Lightdash environments and in some of our CI/CD use cases, being able to refer to "commit tags" in the Github project configuration page would be a big plus. Example: Each project in the 4 env would be pointing at the same repo, same branch, same path, but only the commit tag would differ. Cheers!

👋 Thanks for your message - someone from the Lightdash support team will get back to you asap. Feel free to add any additional context to the thread here in the meantime (screenshots, app version if you're self-hosting etc.).

Hey @Guillaume GO thanks for the suggestion. Let me have a quick chat with the team and then I will get back to you.

Hey @Guillaume GO you could achieve this by using different branches - can you please expand on why you have a preference for referring to commit instead?

Hey @Jess Hitchcock, thanks for asking this. To be clear, it’s just a preference related to our stack, the rationale is we use gitflow as our enterprise standard for CI/CD. For now we're 100% already using 1 branch per env and it's working fine with manual project configurations, it's just that the automation part would be made easier with commit tags being supported as a project config option.

Thanks for clarifying. I have created a feature request for this here which I have upvoted for you.

I've upvoted issue #18772 for you! This issue has been requested by 1 other user. I'll notify everyone here as soon as it's fixed.

thanks @Jess Hitchcock, we appreciate

🗑️ Issue issue #18772 is no longer planned to be fixed.

No one has commented on this in over six months. If it's still something you want, let us know and we'll reopen. For now, separate branches per environment remain the supported way to split dev, staging and prod deployments.

Check out the linked issue for more information.