[FEATURE] Lists should be imported as a single proposal.#4780
Merged
[FEATURE] Lists should be imported as a single proposal.#4780
Conversation
4 tasks
oriolgual
previously approved these changes
Jan 28, 2019
Contributor
|
@tramuntanal since I've merged other PRs there're some conflicts, could you please resolve them? |
oriolgual
previously approved these changes
Jan 28, 2019
3 tasks
oriolgual
previously approved these changes
Jan 31, 2019
Contributor
|
@tramuntanal there're some conflicts after merging other PRs, could you please rebase? |
oriolgual
previously approved these changes
Feb 1, 2019
oriolgual
approved these changes
Feb 1, 2019
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
2 participants
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.
🎩 What? Why?
When importing Participatory Texts, lists should be imported as a single proposal.
📌 Related Issues
📋 Subtasks
CHANGELOGentry📷 Screenshots (optional)