Skip to content

Conversation

@stephenplusplus
Copy link
Contributor

To introduce contributors to our git conventions, our CONTRIBUTING.md
file now links to the AngularJS contributing document.

@ryanseys
Copy link
Contributor

Does every commit require a body and footer?

@ryanseys
Copy link
Contributor

As per the guidelines your commit should be docs(contrib): ... or docs(contributing): ... As docs() and chore() are separate 😄

To introduce contributors to our git conventions, our CONTRIBUTING.md
file now links to the AngularJS contributing document.
@stephenplusplus
Copy link
Contributor Author

Yikes, I should probably read the guide sometime.

@stephenplusplus
Copy link
Contributor Author

Does every commit require a body and footer?

Body - yes, footer - maybe. Up to interpretation, perhaps. The footer is where breaking changes and relevant issues are attached. If there are none, I suppose there isn't anything to put there.

Going to merge. If we want, we can add/elaborate later.

stephenplusplus added a commit that referenced this pull request Sep 18, 2014
docs(contributing): document git commit conventions
@stephenplusplus stephenplusplus merged commit 812bace into googleapis:master Sep 18, 2014

This comment was marked as spam.

This comment was marked as spam.

@stephenplusplus stephenplusplus changed the title docs(chore): document git commit conventions docs(contributing): document git commit conventions Sep 18, 2014
stephenplusplus added a commit that referenced this pull request Sep 18, 2014
Eliminate potential confusion caused by referring to the AngularJS repo.
We also prefer the use of a `common` scope over `app` for library-wide
changes.

Resolves #224
sofisl pushed a commit that referenced this pull request Oct 11, 2022
fix: improve docstrings, and add more field validation
sofisl pushed a commit that referenced this pull request Oct 13, 2022
fix: improve docstrings, and add more field validation
sofisl pushed a commit that referenced this pull request Nov 10, 2022
sofisl pushed a commit that referenced this pull request Nov 10, 2022
sofisl pushed a commit that referenced this pull request Nov 11, 2022
- [ ] Regenerate this pull request now.

PiperOrigin-RevId: 474338479

Source-Link: googleapis/googleapis@d5d35e0

Source-Link: googleapis/googleapis-gen@efcd3f9
Copy-Tag: eyJwIjoiLmdpdGh1Yi8uT3dsQm90LnlhbWwiLCJoIjoiZWZjZDNmOTM5NjJhMTAzZjY4ZjAwM2UyYTFlZWNkZTZmYTIxNmEyNyJ9
sofisl pushed a commit that referenced this pull request Nov 11, 2022
PiperOrigin-RevId: 423128259
Source-Link: googleapis/googleapis@86c3294
Source-Link: googleapis/googleapis-gen@60e75b8
Copy-Tag: eyJwIjoiLmdpdGh1Yi8uT3dsQm90LnlhbWwiLCJoIjoiNjBlNzViODgyYWE0OGNiNzVjODNkOTRhOWUzYTIwYzk5NjM2Y2FmMCJ9
See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md
Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>
sofisl added a commit that referenced this pull request Nov 16, 2022
samples: pull in latest typeless bot, clean up some comments

Source-Link: googleapis/synthtool@0a68e56
Post-Processor: gcr.io/cloud-devrel-public-resources/owlbot-nodejs:latest@sha256:5b05f26103855c3a15433141389c478d1d3fe088fb5d4e3217c4793f6b3f245e

Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>
Co-authored-by: sofisl <55454395+sofisl@users.noreply.github.com>
Co-authored-by: gcf-merge-on-green[bot] <60162190+gcf-merge-on-green[bot]@users.noreply.github.com>
sofisl pushed a commit that referenced this pull request Jan 27, 2026
sofisl pushed a commit that referenced this pull request Jan 27, 2026
miguelvelezsa pushed a commit that referenced this pull request Jan 29, 2026
This PR was generated using Autosynth. 🌈

Synth log will be available here:
https://source.cloud.google.com/results/invocations/c36c6dbc-ab79-4f17-b70b-523b420b2a70/targets

- [ ] To automatically regenerate this PR, check this box.

Source-Link: googleapis/synthtool@5747555
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants