LISTSERV mailing list manager LISTSERV 16.5

Help for CODE4LIB Archives


CODE4LIB Archives

CODE4LIB Archives


CODE4LIB@LISTS.CLIR.ORG


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

CODE4LIB Home

CODE4LIB Home

CODE4LIB  June 2020

CODE4LIB June 2020

Subject:

Re: [EXTERNAL] Re: [CODE4LIB] Anti-racist terminology changes: update "master" to "main" branch

From:

Tammy Metz <[log in to unmask]>

Reply-To:

[log in to unmask]

Date:

Fri, 26 Jun 2020 16:22:28 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (83 lines)

Hi Demian,
  
 A way to redirect links that contain a deleted branch name to the equivalent link on the repository's default branch does not exist yet, but it is being worked on!  So stay tuned. 
  
 I agree that making this change can have unintended consequences, so it's best to carefully think it through before acting.  I had one person write in who had changed the master branch name to main, and it closed all of her pull requests because the master branch didn't exist anymore.  She couldn't change the base branch because you can't change the base branch of a closed pull request.  It was a mess (hindsight solution: change the base branch of all pull requests *before* getting rid of the master branch; in other words, don't rename, but have both master and main branches exist until you are confident in deleting master).  She was eventually able to work it out, but it certainly caused a lot of frustration.
  
 I will be very happy when we release official guidance on this, and have my fingers crossed that it will be soon.
  
 As for Eric's email about GitHub Pages, they are as we speak working on allowing you to select any branch to publish Pages from.  I don't know when this change is going to ship, but I am very excited about it, because this has really been needed in Pages for a long time no matter what your branches are named, and it will offer a lot more flexibility for people.

--- Tammy Metz
 505-715-0999
 [log in to unmask]

  

----------------------------------------
 From: "Demian Katz" <[log in to unmask]>
Sent: Friday, June 26, 2020 8:10 AM
To: [log in to unmask]
Subject: Re: [CODE4LIB] [EXTERNAL] Re: [CODE4LIB] Anti-racist terminology changes: update "master" to "main" branch   
Thanks for the update, Tammy!

Can you clarify whether there is an existing mechanism, or future plans, for redirecting from one branch name to another?

My use case is this: I am interested in making the branch name change, but my project has close to a decade of legacy in terms of links to specific code files in GitHub (in wiki pages, ticket comments, listserv messages, etc.). Many of these links include the branch name "master," and cleaning them all up is probably impossible (I can't change history in listserv archives, for example, but those old messages still contain valid/useful information that people actively rely on). Even those links that are within my control are distributed across multiple systems and could take a long time to comprehensively track down and fix, so having a transition plan would be really helpful.

I'd love to be able to move away from master going forward, but to have pre-existing master links seamlessly redirect to a new branch name instead of just 404ing. Otherwise, I'm caught in the uncomfortable situation of weighing the costs and benefits of keeping the name (and alienating people through potentially offensive terminology) vs. changing the name (and potentially alienating people through the frustration of broken links when they are looking for solutions).

I'm hoping that this situation is being accounted for in your planning, but I also recognize that it might not be trivially easy to support. I'd love to hear that there's already a solution for this use case, though; that would make my week. ??

In any case, thanks for your support!

- Demian

-----Original Message-----
From: Code for Libraries <[log in to unmask]> On Behalf Of Tammy Metz
Sent: Thursday, June 25, 2020 2:38 PM
To: [log in to unmask]
Subject: [EXTERNAL] Re: [CODE4LIB] Anti-racist terminology changes: update "master" to "main" branch

Hi! I recently left the library world and started working at GitHub, and I just wanted to clarify that while this is being worked on, the switch has not yet been pulled! Our engineers are working hard to make they are dotting their "i"s and crossing their "T"s so nothing unexpected happens when this change is rolled out. I believe this will happen in about another month.

Here is the "official" statement we have right now:

---
We are actively working alongside the Git project itself, as well as other version control vendors, on making three changes in GitHub:
(1) we are changing the default branch name for new repos away from 'master'
(2) we are making it easy for users to choose their own default branch name for all new repos created
(3) we are releasing guidance and tools for users who may choose to rename their default branch in existing repos.
---

There have been many organizations that have gone ahead and successfully made this change to their existing repositories already, but I just want to be clear that this change hasn't happened yet on GitHub's end.

Tammy Metz, MLIS
Developer Support Engineer
GitHub

----------------------------------------
From: "Caffrey-Hill, Julia" <[log in to unmask]>
Sent: Thursday, June 25, 2020 11:05 AM
To: [log in to unmask]
Subject: [CODE4LIB] Anti-racist terminology changes: update "master" to "main" branch
Hi Code4Lib Community,
GitHub recently announced changes to its default branch name, from "master" to "main". This CNET article by Shelby Brown<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.cnet.com%2Fnews%2Fmicrosofts-github-is-removing-coding-terms-like-master-and-slave%2F&amp;data=02%7C01%7Cdemian.katz%40VILLANOVA.EDU%7Cba3cba051ebb402bafd908d81936db8f%7C765a8de5cf9444f09cafae5bf8cfa366%7C0%7C1%7C637287070692755763&amp;sdata=MRMVWY8OGFyYMROsT2b2MWNWnsNEjqOJre1QrHQmVNk%3D&amp;reserved=0> covered these and other anti-racist terminology changes occurring in the larger dev community as proposed by Una Kravets, Google Chrome developer.

GitHub will not update existing repositories. For this reason, I suggest the following updates:

* Update the name of the default branch of your code repositories' and your organizations' repositories from "master" to "main". It is easy to rename the default branch. I recommend these instructions written by Alexis Moody<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdev.to%2Fafrodevgirl%2Freplacing-master-with-main-in-github-2fjf&amp;data=02%7C01%7Cdemian.katz%40VILLANOVA.EDU%7Cba3cba051ebb402bafd908d81936db8f%7C765a8de5cf9444f09cafae5bf8cfa366%7C0%7C1%7C637287070692755763&amp;sdata=%2FiLMMSo1IODNhoylr5ubBV4Ukr87y2yraM%2B59t1m158%3D&amp;reserved=0>. I followed these for my personal repositories, adding a git status, git pull beforehand, and it was very straightforward. For group or organization repositories, you may want to coordinate timing with other maintainers.

* Update your documentation. If your documentation contains references to the "master" branch, these should be updated.

Your support in moving to terminology without historical baggage or racist symbolism would benefit present and future developers who fork or update code. It's also shorter! While this small update is not exhaustive of what we can do to be a more inclusive community, it would bring us into alignment with a decision made by GitHub, a platform Code4Lib uses that has taken a stand against racism.

Please contact me if you want a video tutorial demonstrating to do this, or if you would like me to add it as an issue in a Code4Lib community repository.

Thanks,
Julia Caffrey-Hill
Web Services Librarian
Towson University
Twitter: @jcaffreyhill

 

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003

ATOM RSS1 RSS2



LISTS.CLIR.ORG

CataList Email List Search Powered by the LISTSERV Email List Manager