Age | Commit message (Collapse) | Author |
|
PiperOrigin-RevId: 350197814
|
|
For validation, the "on" key in existing YAML files is changed to a literal
string. In the YAML spec, on is a keyword which encodes a boolean value, so
without relying on a specific implementation the YAML files are technically
not encoding an object that complies with the specification.
PiperOrigin-RevId: 350172147
|
|
This GitHub action has been failing since 4e963c9.
PiperOrigin-RevId: 349327675
|
|
Also, drop the pull_request template, since this has not proved to be
helpful, and just results in a commit message the includes the list.
PiperOrigin-RevId: 347636507
|
|
PiperOrigin-RevId: 342577869
|
|
When nogo checks are violated, they will automatically posted
as annotations on the specific GitHub commit. This allows us
to ensure analysis & style rules and have them called out.
PiperOrigin-RevId: 334447285
|
|
runsc -v doesn't work. It should be runsc -version
PiperOrigin-RevId: 331911035
|
|
We can't actually push the Go branch on pushes to feature branches.
Signed-off-by: Andrei Vagin <avagin@google.com>
|
|
Signed-off-by: Andrei Vagin <avagin@google.com>
|
|
bazel creates sysmlink to the cache on the first invokation.
On a new clone, there are no symlink, thus `rm -rf bazel-bin/gopath`
has no effect. Call `bazel build something` first, then delete
cached gopath.
PiperOrigin-RevId: 327536044
|
|
PiperOrigin-RevId: 324642975
|
|
PiperOrigin-RevId: 324615016
|
|
PiperOrigin-RevId: 324302828
|
|
PiperOrigin-RevId: 324024075
|
|
Fixes #3326
PiperOrigin-RevId: 323589669
|
|
Add a conditional to avoid running the issue reviver on forks. It will
always cause errors since bug references in the source code don't match
issue IDs in forked repos.
PiperOrigin-RevId: 321042060
|
|
PiperOrigin-RevId: 315020368
|
|
PiperOrigin-RevId: 313419745
|
|
Fixes #2722
|
|
PiperOrigin-RevId: 312159017
|
|
PiperOrigin-RevId: 312155686
|
|
PiperOrigin-RevId: 311600872
|
|
Otherwise the labeller will generate an error each time.
PiperOrigin-RevId: 309505731
|
|
This is the first automated GitHub actions workflow, and it simply applies
labels to pull request in a best-effort fashion.
PiperOrigin-RevId: 308112191
|
|
This just provides some sane reminders and ticks a box on the GitHub UI. This
change also cleans up the issue template, as there is already an automatic
link to the repository's security disclosure policy.
PiperOrigin-RevId: 307868833
|
|
This allows us to specify a richer configuration for the issue template, that
effectively moves a lot of the "metadata" from the template itself to the main
issue page.
PiperOrigin-RevId: 307666509
|
|
PiperOrigin-RevId: 250730726
|
|
PiperOrigin-RevId: 242690968
Change-Id: I1ac2248b5ab3bcd95beed52ecddbb9f34eeb3775
|
|
PiperOrigin-RevId: 195735915
Change-Id: If4dcd836c3cf9da7c314b95101b23f95ff0eb234
|
|
When editing the bug, the rendered view of the tags don't show up. This format is easier to read.
PiperOrigin-RevId: 195697019
Change-Id: If9bb818b7ecd28bb87608a52b3343d488144ebfd
|
|
PiperOrigin-RevId: 195444658
Change-Id: I62d12405324f9c80ec572c65d76c5f320a9b549e
|
|
PiperOrigin-RevId: 195382309
Change-Id: I3e50206d137bb15c0532282ffbc3508aa5ddeb28
|
|
It directs users to our contributor guidelines and Gerrit instance.
PiperOrigin-RevId: 194830523
Change-Id: I9882da0e95d04f7e1ee941bf65d40fbe45a47b24
|