Request for Sourceware Git access to run the Binutils try builder
Project / Subsystem
binutils / binutils
Date
2026-10-05
Proposer
Harshit Kumar <harshit7kr@gmail.com>
Source type
public_inbox
Consensus
Under Review
Sentiment
7/10
Technical tradeoffs
- • Establishing clear CI workflows for external contributors without direct Git access can increase the project's onboarding friction but ensures patches are tested before merging.
All attributes
- project
- binutils
- subsystem
- binutils
- patch_id
- —
- discussion_id
- CAOX--DRrBRN5C-ph+wuZbMGGnLrFj_ApHwAC+ZYgioF-0YbTJw@mail.gmail.com
- source_type
- public_inbox
- title
- Request for Sourceware Git access to run the Binutils try builder
- headline
- Request for Sourceware Git access to run the Binutils try builder
- tldr
- Harshit Kumar requests guidance on obtaining Sourceware Git access to run the Binutils try builder for a submitted patch.
- proposer
- Harshit Kumar <harshit7kr@gmail.com>
- consensus
- Under Review
- outcome
- under_review
- sentiment_score
- 7
- technical_tradeoffs
-
- • Establishing clear CI workflows for external contributors without direct Git access can increase the project's onboarding friction but ensures patches are tested before merging.
- series_id
- —
- series_role
- standalone
- series_parts
- []
- tags
-
- • CI
- • contributor workflow
- • git access
- • patch testing
- bugzilla_url
- —
- date
- 2026-10-05T00:00:00.000Z
Request for Sourceware Git access to run the Binutils try builder
Harshit Kumar has submitted a patch to binutils and wishes to test it using the project’s try builder. He is seeking Sourceware Git SSH access to push a temporary branch for this purpose and is asking for assistance from a maintainer or clarification on the correct process, as his Sourceware Bugzilla account is active but Git access is missing. The discussion evolves to explore alternative workflows for contributors without direct Git push access.