Skip to content
This repository has been archived by the owner on Oct 11, 2023. It is now read-only.

processbot features which are intended to be removed or deprecated #356

Open
2 of 4 tasks
joao-paulo-parity opened this issue Jan 10, 2022 · 1 comment
Open
2 of 4 tasks
Labels
documentation Improvements or additions to documentation

Comments

@joao-paulo-parity
Copy link
Contributor

joao-paulo-parity commented Jan 10, 2022

Deprecated

Removed

Could be removed, but requires more work

Suggestions

  • bot rebase (or any other developer-facing merge-automation task) could be moved to another project focused on event processing (front-end) so that processbot can focus on the backend processing of the companion build system
@joao-paulo-parity joao-paulo-parity pinned this issue Jan 11, 2022
@TriplEight
Copy link
Contributor

bor merge (or bor merge $branch) comment. My idea is the backend should be implemented within pre-merge pipelines tool. Whereas the "frontend" as in reading the comment from PR should remain in the processor.

  1. this logic is already implemented in pre-merge pipelines tool
  2. the result of bot merge does the same as the pre-merge tool (but also pushes the commit). So it can do all the following tool's activities. And then one can put the automerge label and it merges if all goes well.

@joao-paulo-parity joao-paulo-parity added the documentation Improvements or additions to documentation label Mar 25, 2022
@Vovke Vovke added duplicate This issue or pull request already exists and removed duplicate This issue or pull request already exists labels Apr 12, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

3 participants