Introduce transformChanges to campaign spec (RFC 265)#398
Merged
Conversation
a024399 to
a52e9e9
Compare
Contributor
Author
|
Just updated this to use the |
a52e9e9 to
b635d03
Compare
ceb46fa to
a5269a2
Compare
Contributor
Author
|
@sourcegraph/campaigns @rrhyne This is now ready for review. Please see the PR description for what's included and what's not. Documentation and schema update in |
LawnGnome
approved these changes
Dec 10, 2020
Co-authored-by: Adam Harvey <aharvey@sourcegraph.com>
scjohns
pushed a commit
that referenced
this pull request
Apr 24, 2023
* Add transformChanges to campaign spec * Update Executor integration test * Add a failing test for code transformations * Change execution cache to only cache diffs * Rename from .patch to .diff * Extract groupFileDiffs function * Add test for GroupFileDiffs * Add some comments * Fix campaign progress printer for multiple changeset specs * Display how many changeset specs were produced in one repo * Add more tests for grouping changes * Fix problems after rebase * Switch from branchSuffix to branch * Add a repository filter to the transformChanges.Group * Check whether transformChanges is supported * Validate that multiple changesets don't have same branch * Add minLength to campaign spec * Pluralize message correctly * Update internal/campaigns/executor.go Co-authored-by: Adam Harvey <aharvey@sourcegraph.com> * Update feature date * Add a changelog entry Co-authored-by: Adam Harvey <aharvey@sourcegraph.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

This is the implementation of the suggested solution for Option B in RFC 265: Multiple changesets per repository to produce multiple changesets in a single repository.
It depends on https://github.com/sourcegraph/sourcegraph/pull/16235. It fixes https://github.com/sourcegraph/sourcegraph/issues/14970.
IMPORTANT: this only implements the first step in "Defintion of success". It does not yet implement addressing multiple changesets in the same repository separately (that's Part2 in the RFC).
What this does is to introduce the
transformChangesproperty to campaign specs (see https://github.com/sourcegraph/sourcegraph/pull/16235 for schema change on server).Here is an example campaign spec using it:
Changelog of this PR
branchproperty instead ofbranchSuffixto incorporate feedback on RFC 265.repositoryattribute to thegroup.