bazel-contrib / bazel-contrib/rules_go

Analysis phase improvements for rules

Open
#4,013 21 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
1.5k
Forks
760
Avg merge
1d 11h
Merged PRs (30d)
12

Description

### What version of rules_go are you using?
Tip

### What version of gazelle are you using?
n/a

### What version of Bazel are you using?
7.3 rc1

### Does this issue reproduce with the latest releases of all the above?

yes

### What operating system and processor architecture are you using?

darwin arm64

### What did you do?
`bazel build --nobuild --starlark_cpu_profile`

### What did you expect to see?
A relatively clean profile

### What did you see instead?
Opportunities to improve things

Contributor guide

Open the contributing guide

Research direction

Start by reproducing `bazel build --nobuild --starlark_cpu_profile` on the stated Bazel and darwin arm64 setup, then inspect the generated profile. The issue names no files, tests, or specific profile changes; completion would require identifying and agreeing on concrete analysis-phase improvements.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
build-system
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.