golang/go

x/build/cmd/gerritbot: commit message source confuses a lot of people

Open

#25,359 opened on May 11, 2018

View on GitHub
 (17 comments) (0 reactions) (0 assignees)Go (19,008 forks)batch import
BuildersNeedsInvestigationhelp wanted

Repository metrics

Stars
 (133,883 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Mapping from the title/first comment -> Gerrit commit message is confusing to almost everyone. It would be nice if this were either more clear or the commit message was determined by a more user-friendly method. Since PRs can have multiple commits, squashing all commit messages into one for the final commit message is one solution.

Open to thoughts on others.

/cc @bradfitz @bcmills @FiloSottile

Contributor guide

Research direction
Understand how the current commit message mapping from Gerrit to GitHub works in x/build/cmd/gerritbot. Investigate alternatives like squashing all commits into one message. Propose a clear method.
Tech stack
go
Domain
backenddeveloper experiencetooling
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Go
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60