Currently, if a project has a latest branch in its repo, we treat that branch
as the source for the latest version implicitly. This pattern originated as a
way to provide projects with some flexibility when the repository naming
conventions weren't supported by our implicit version handling logic.
With automation rules allowing for more configuration, and perhaps custom
version slugs helping as well, it feels like we could make this feature
configurable or deprecate it.
This might also fit in with #5319 where we have talked about surfacing our
implicit rules as explicit rules.
An example of what this might look like on the automation rules admin
Front conversations
Currently, if a project has a
latestbranch in its repo, we treat that branchas the source for the
latestversion implicitly. This pattern originated as away to provide projects with some flexibility when the repository naming
conventions weren't supported by our implicit version handling logic.
With automation rules allowing for more configuration, and perhaps custom
version slugs helping as well, it feels like we could make this feature
configurable or deprecate it.
This might also fit in with #5319 where we have talked about surfacing our
implicit rules as explicit rules.
An example of what this might look like on the automation rules admin