We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Commits can be created very often (e.g. in documents), and that's great for things like live synchronization. However, it also has some downsides:
Perhaps we should have a way to combining / merging / trimming commits. This essentially means changing the history, in a way.
I'm not quite sure where this should happen. I think it should probably be a feature of atomic-server, but it also has spec implications.
So perhaps we have a /shorten-commits endpoint, which gets a Subject and some options (max count of commits, or max time gap).
/shorten-commits
It then iterates over all commits, builds new commits and signs these server side, once every N commits (depending on date delta).
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Commits can be created very often (e.g. in documents), and that's great for things like live synchronization. However, it also has some downsides:
Perhaps we should have a way to combining / merging / trimming commits. This essentially means changing the history, in a way.
I'm not quite sure where this should happen. I think it should probably be a feature of atomic-server, but it also has spec implications.
So perhaps we have a
/shorten-commits
endpoint, which gets a Subject and some options (max count of commits, or max time gap).It then iterates over all commits, builds new commits and signs these server side, once every N commits (depending on date delta).
The text was updated successfully, but these errors were encountered: