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

docs: fix namespace size in comment (backport #2357) #2360

Merged
merged 1 commit into from
Aug 25, 2023

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Aug 25, 2023

This is an automatic backport of pull request #2357 done by Mergify.


Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

Closes #2348

## Overview
After versioned namespaces were implemented, namespaces shrank from 33
bytes to 29 bytes. Fixed that in the comment section of event.proto

---------

Co-authored-by: Rootul P <rootulp@gmail.com>
(cherry picked from commit fae4a80)
@github-actions github-actions bot added the bot item was created by a bot label Aug 25, 2023
@celestia-bot celestia-bot requested a review from a team August 25, 2023 14:40
@evan-forbes
Copy link
Member

I feel like we've a bit inconsistent with backporting documention, which is ok. Do we want to be consistent tho? like, we always backport all docs, or only code comment, or specs but not adrs etc

@rootulp
Copy link
Collaborator

rootulp commented Aug 25, 2023

Agreed we have been inconsistent. My initial reaction is: we should backport as much as possible to minimize the diff between main and v1.x. In other words, main should only have the breaking changes that can't be applied to v1.x. Everything else (docs, specs, ADRs) we backport.

@rootulp rootulp enabled auto-merge (squash) August 25, 2023 15:12
@rootulp rootulp merged commit b447b9b into v1.x Aug 25, 2023
22 checks passed
@rootulp rootulp deleted the mergify/bp/v1.x/pr-2357 branch August 25, 2023 15:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bot item was created by a bot
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants