Skip to content
This repository was archived by the owner on Sep 30, 2024. It is now read-only.

CampaignSpecFields should include the importChangesets field #13009

Closed
chrispine opened this issue Aug 14, 2020 · 1 comment
Closed

CampaignSpecFields should include the importChangesets field #13009

chrispine opened this issue Aug 14, 2020 · 1 comment
Assignees
@chrispine
Labels
batch-changes Issues related to Batch Changes estimate/1d planned/3.20
Milestone
Campaigns Sprint 2

Comments

@chrispine
Copy link
Contributor

The campaign spec schema now includes an importChangesets field. The CampaignSpecFields type should include this.
@chrispine chrispine added the batch-changes Issues related to Batch Changes label Aug 14, 2020
@eseliger eseliger added this to the 3.20 milestone Aug 18, 2020
@eseliger eseliger added dependencies Pull requests that update a dependency file estimate/0.5d campaigns and removed dependencies Pull requests that update a dependency file labels Aug 18, 2020
@mrnugget mrnugget self-assigned this Aug 19, 2020
@chrispine chrispine mentioned this issue Aug 19, 2020
Closed
52 tasks
@chrispine chrispine assigned chrispine and unassigned mrnugget Aug 19, 2020
@chrispine chrispine modified the milestones: 3.20, 3.21 Sep 10, 2020
@sourcegraph-bot sourcegraph-bot mentioned this issue Sep 15, 2020
Closed
14 tasks
@chrispine chrispine modified the milestones: 3.21, Campaigns Sprint 1 Sep 16, 2020
@sourcegraph-bot sourcegraph-bot mentioned this issue Oct 6, 2020
Closed
24 tasks
@chrispine
Copy link
Contributor Author

Looks like @LawnGnome fixed this in #13476 😄

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@chrispine chrispine

Labels
batch-changes Issues related to Batch Changes estimate/1d planned/3.20
Projects
None yet
Milestone
Campaigns Sprint 2
Development

No branches or pull requests
3 participants
@mrnugget @chrispine @eseliger