Skip to content

Conversation

@bkuhlmann
Copy link
Contributor

Overview

This article details how to use git for-each-ref in new and interesting ways (including the new is-base field).

Details

I published this article earlier today so thought it might be of interest to folks here too.

@LemmingAvalanche
Copy link
Contributor

I skimmed it and it looks like an interesting edition to the newsletter. This is a command that probably needs more exposure.

Thanks.


<!---
__Easy watching__
-->
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please don't remove such commented sections. They are commented because we might want to uncomment them if we have relevant content (here videos) to put in them, and it's still possible at this point that we will have such content.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, apologies. Fixed. Was too hasty and accidentally deleted that section.

@chriscool
Copy link
Collaborator

@bkuhlmann thanks for the suggestion and @LemmingAvalanche thanks for your opinion on it. I will let @jnareb decide on this though as he is responble for the link.

This article details how to use `git for-each-ref` in new and interesting ways (including the new `is-base` field).
@chriscool
Copy link
Collaborator

@bkuhlmann I had to fix the link to Git 2.47.0 Release Notes in 36edbf5.

@bkuhlmann bkuhlmann deleted the git_for_each_ref branch November 1, 2024 22:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants