Skip to content

feat: handle GitHub username changes gracefully in governance sync #220

@RAWx18

Description

@RAWx18

Feature Summary

When a contributor changes their GitHub username, the governance sync currently risks treating the new and old usernames as different contributors. The steward/governance sync should automatically detect username changes and merge history correctly without creating duplicate records.

Use Case / Problem

  • Contributor changes their GitHub username
  • Next governance sync runs
  • Sync processes contributor data

Old and new usernames may be treated as separate contributors, resulting in split history or duplicate records.

Suggested Solution

Username change is detected and the contributor’s history, role, and records are updated seamlessly under the new username.

Alternatives Considered

No response

Additional Context

  • Governance sync should use a stable identifier (e.g. GitHub user ID) internally and map usernames as mutable fields.

  • On detecting a username change:

    • Update contributors.yaml to the new username
    • Preserve and merge full contribution and governance history
    • Avoid creating new contributor entries or conflicting history
  • This is critical for long-term governance accuracy, auditability, and contributor trust.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions