Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Collaboration by forking/merging annotations #5819

Open
Tracked by #7619
philippotto opened this issue Nov 1, 2021 · 1 comment
Open
Tracked by #7619

Collaboration by forking/merging annotations #5819

philippotto opened this issue Nov 1, 2021 · 1 comment

Comments

@philippotto
Copy link
Member

philippotto commented Nov 1, 2021

In the context of proofreading, we should re-evaluate this idea. I wrote a design doc draft here which is more up to date.

Old issue content:

For a public annotation, users can do "copy to my account" to make changes (e.g., fixes). However, there is no way to stream these changes back in a pull-request fashion.

Currently, one has to send a mail with the "forked" annotation and the owner has to re-apply these changes manually.

Different possibilities to better support this use case could be:
- allow to create some kind of "pull request" which the owner can accept
- support "merging" multiple PRs which are based on a common base version (but there are no conflicts)
- support resolving conflicts if the PRs don't agree in certain aspects

Tangentially related: It would be cool to see a list of "forks" of one annotation. Only if the forker has allowed this probably.
@fm3 fm3 changed the title Enable fork&pull request workflow Enable fork&pull request workflow for annotations Nov 4, 2021
@philippotto philippotto self-assigned this May 28, 2024
@philippotto philippotto changed the title Enable fork&pull request workflow for annotations Collaboration by forking/merging annotations May 28, 2024
@philippotto
Copy link
Member Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants