fonsdant commented on PR #17204: URL: https://github.com/apache/kafka/pull/17204#issuecomment-2366967094
How about using only a ref to point to the cached commit instead? A tag isn't the best option, as described in the GitHub REST API documentation: _"A Git tag is similar to a Git reference, but the Git commit it points to never changes."_ A branch doesn’t seem ideal either, since we're not using it for its intended features. We’ve created the branch solely to mark the cached commit, and there’s also the risk of merge conflicts. So, a ref seems to be a great option. It acts as an "alias" for the cached commit and can be updated to point to a new cached commit. What do you think? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
