[GitHub] [couchdb] nickva commented on pull request #4355: chore: protect 3.3.x and 3.2.x branches

2023-05-10 Thread via GitHub
nickva commented on PR #4355: URL: https://github.com/apache/couchdb/pull/4355#issuecomment-1542647218 This commit was on 3.3.x but it never merged into main. When merged a few bits we forgot from 3.3.x into main https://github.com/apache/couchdb/pull/4593 we brought this change in.

[GitHub] [couchdb] nickva commented on pull request #4355: chore: protect 3.3.x and 3.2.x branches

2023-01-07 Thread GitBox
nickva commented on PR #4355: URL: https://github.com/apache/couchdb/pull/4355#issuecomment-1374680076 @big-r81 3.2.2-docs might not be a proper 3.2.x branch. It's sort of almost 3.3.x (main) but with docs pointing to 3.2.2. This is to let us update and add 3.2.2 doc updates without having

[GitHub] [couchdb] nickva commented on pull request #4355: chore: protect 3.3.x and 3.2.x branches

2023-01-06 Thread GitBox
nickva commented on PR #4355: URL: https://github.com/apache/couchdb/pull/4355#issuecomment-1373978465 Good idea to encourage using rebases if possible, especially for small or medium PR. But it could just be an admonishment rather than an enforcement. I can see in cases when large