Skip to content
This repository was archived by the owner on Dec 8, 2021. It is now read-only.

doc: describe how to create a patch release#221

Merged
coryan merged 2 commits intogoogleapis:masterfrom
coryan:doc-patch-release-process
Mar 10, 2020
Merged

doc: describe how to create a patch release#221
coryan merged 2 commits intogoogleapis:masterfrom
coryan:doc-patch-release-process

Conversation

@coryan
Copy link
Contributor

@coryan coryan commented Mar 10, 2020

This change is Reviewable

@googlebot googlebot added the cla: yes This human has signed the Contributor License Agreement. label Mar 10, 2020
@codecov
Copy link

codecov bot commented Mar 10, 2020

Codecov Report

Merging #221 into master will decrease coverage by 0.01%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #221      +/-   ##
==========================================
- Coverage   96.28%   96.26%   -0.02%     
==========================================
  Files          97       97              
  Lines        4443     4447       +4     
==========================================
+ Hits         4278     4281       +3     
- Misses        165      166       +1
Impacted Files Coverage Δ
google/cloud/internal/parse_rfc3339_test.cc 92% <0%> (-0.71%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 99ed239...1789ca7. Read the comment docs.

@coryan
Copy link
Contributor Author

coryan commented Mar 10, 2020

Thanks for the review, much better. I made some more edits than you asked, PTAL.

@coryan coryan merged commit 6ee9ec8 into googleapis:master Mar 10, 2020
@coryan coryan deleted the doc-patch-release-process branch March 10, 2020 19:59
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

cla: yes This human has signed the Contributor License Agreement.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants