config-production: prepare thunderbird-desktop sync configuration (bug 2042254)#122
config-production: prepare thunderbird-desktop sync configuration (bug 2042254)#122shtrom wants to merge 1 commit into
Conversation
|
@coreycb @dandarnell would you mind having a look at this PR? It's the rule that will sync commits from GitHub to a specific repo in HgMO. Pay particularl attention to the source and target repositories, as well as the patterns. I have kept the tagging rules pretty broad, but we can make them more specific if you prefer. (Don't worry about the |
shtrom
force-pushed
the
bug2042254/thunderbird-config
branch
from
8459c5e to
fc335df
Compare
shtrom
force-pushed
the
bug2042254/thunderbird-config
branch
from
fc335df to
5b7804d
Compare
|
|
||
| [[tag_mappings]] | ||
| source_url = "https://github.com/thunderbird/thunderbird-desktop.git" | ||
| tag_pattern = "(^THUNDERBIRD|NIGHTLY|RELEASE|RELEASE)_.*$" |
There was a problem hiding this comment.
Just to note, and I think we discussed this before, but iirc the reason BETA_ isn't included here is because the tags will have already been brought in by the beta branch sync. Whereas in comm-release you'll see the BETA_ tags https://hg-edge.mozilla.org/releases/comm-release/tags
There was a problem hiding this comment.
But with that said, NIGHTLY is in here, so maybe we should add BETA_ ?
|
|
||
| [[tag_mappings]] | ||
| source_url = "https://github.com/thunderbird/thunderbird-desktop.git" | ||
| tag_pattern = "^ESR_(\\d+)_BASE$" |
There was a problem hiding this comment.
Should this include THUNDERBIRD_ as well?
https://hg-edge.mozilla.org/releases/comm-esr140/tags
|
|
||
| [[tag_mappings]] | ||
| source_url = "https://github.com/thunderbird/thunderbird-desktop.git" | ||
| tag_pattern = ".+" |
There was a problem hiding this comment.
General question.. why not just pull in all tags for each branch?
2 participants
No description provided.