Hacktoberfest 2026:メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Users should be able to change their associated data

オープン
#50 コメント 2 件 リアクション 0 件 担当者 1 名 GitHub で見る

@ajdlinux がすでに取り組んでいます。

2019年11月27日 から。

評価

この issue はまだ評価されていません。

説明

enhancement

Users should be able to change their associated data, like name and email, and not be stuck with one name forever. I'm quoting some bits here with a few comments on my own:

To try and put it simply, the author of a commit is tied in to the identity of the commit itself. If you change the author, it’s treated as an entirely new commit. Anyone who has grabbed a copy of your original commit and made subsequent changes on top of it finds themselves orphaned from the history of the project. To use a crude analogy, it’s like you rip the trunk of a tree out, while the branches are magically left hanging in the air, connected to nothing and isolated.

Of course, it’s not that the designers of Git tried to make it difficult for committers to change their names. It’s likely that most of them just didn’t think about what would happen if a developer needed to change their name retroactively, because most of the people who have worked on Git are cis men. They aren’t expected to change their names if and when they get married or divorced, and having cis privilege, they don’t need to change their name to something more consistent with their gender. Nevertheless, the inability to change one’s name retroactively without disrupting others’ work can mean that trans people — particularly trans women, who are likely to face harsh social stigma in any space where their trans history is known — will have to cease to contribute to their projects when they transition.

*additions by ng0:
Additionally this means that if your project has an open policy on names and you decide to change your name you will be stuck in the patchworks interface with the old name. In my case as I do not want to use my legal name due to personal reasons,it created this situation:
before signing up at patchwork, the authors name was "ng0".
Then I signed up, the process was unclear to me so I chose "non" "such" thinking i could change it later on.. after signing up I am now stuck with "non such".

I had no chance to test this myself, but you should also be aware of names which differ from the first+lastname form.

References: #49 and https://libreboot.org/git/#guidelines

主要言語
Python
スター
317
フォーク
91
PR マージ指標
30日以内にマージされた PR はありません

コントリビューションガイド

コントリビューションガイドを開く

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

getpatchwork/patchwork のほかの issue

getpatchwork/patchwork の issue をすべて見る

似ている issue

Python の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。