{"push_id":2382045535,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"e2d200f32a7242898a5c976837bd3b8e6dfed62c","before":"a854d6c0d3d222bbd4ff2a532d48ddd91718908c","commits":[{"sha":"e2d200f32a7242898a5c976837bd3b8e6dfed62c","author":{"name":"cparsons","email":"afa8e4b38729b866bf53d2760c9e90b2cfa9a2cc@google.com"},"message":"Expose an actions provider on RuleConfiguredTarget instances.\n\nGiven a target (for example from a skylark aspect), one will be able to access a list of actions that the target generated using \"target.actions\". This is without additional memory footprint.\n\nActions themselves are not fully exposed to skylark (and thus there isn't much meaning to gather from them in skylark yet). Access methods will follow soon.\n\nRELNOTES: None.\nPiperOrigin-RevId: 188098079","distinct":true,"url":"https://api.github.com/repos/bazelbuild/bazel/commits/e2d200f32a7242898a5c976837bd3b8e6dfed62c"}]}
{"actor":{"display_login":"bazel-io"}}