Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix a row in the job patterns table #336

Merged
merged 1 commit into from
Apr 11, 2016

Conversation

dougkoch
Copy link
Contributor

@dougkoch dougkoch commented Apr 7, 2016

In the raw Markdown, the row for the "Queue with Variable Pod Count" pattern has one more column than the other rows. The extra empty cell (in column 2) shifts the checkmarks one column to the right of where they should be. Reading through the example of how this job pattern works, it's clear that columns 2, 3, and 5 are the ones that should be checked.

The row for the "Queue with Variable Pod Count" pattern has one more
column than the other rows. The extra column shifts the checkmarks one
column to the right of where they should be.
@googlebot
Copy link

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.


  • If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
  • If you signed the CLA as a corporation, please let us know the company's name.

@dougkoch
Copy link
Contributor Author

dougkoch commented Apr 7, 2016

I signed it!

@googlebot
Copy link

CLAs look good, thanks!

@johndmulhausen
Copy link

Thanks, @dougkoch !

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.

3 participants