This sounds great! Thanks @driazati!!
---
[Visit
Topic](https://discuss.tvm.apache.org/t/rfc-allow-merging-via-pr-comments/12220/3)
to respond.
You are receiving this because you enabled mailing list mode.
To unsubscribe from these emails, [click
here](https://discuss.tvm.apache.org/ema
This sounds good to me. AFAIK, PyTorch also leverages this approach so it might
not be that "non-standard" 😜
---
[Visit
Topic](https://discuss.tvm.apache.org/t/allow-merging-via-pr-comments/12220/2)
to respond.
You are receiving this because you enabled mailing list mode.
To unsubscribe
# [RFC] Merge Bot
## Summary
PRs authors must currently wait for changes to be manually merged by a
committer clicking the "merge" button. A large amount of time can often elapse
between CI going green, a PR being approved, and this merge button being
pressed. This RFC proposes a safe, self-
TVM has two methods of user engagement today:
* GitHub [PRs](https://github.com/apache/tvm/pulls) and
[Issues](https://github.com/apache/tvm/issues)
* The [Discuss forum](https://discuss.tvm.apache.org/)
Historically both GitHub and Discuss have been used to develop on TVM, with
design discus
We discussed this at the TVM Community Meeting this morning. There was a
presentation about the approach followed by some discussion. Thanks @MJKlaiber
@cgerum @SebastianBoblestETAS @paulpb @PhilippvK @r.stahl @aca88 for bringing
this to the meeting!
Here are some notes (please feel free to c
[quote="manupa-arm, post:11, topic:12039"]
[quote="MJKlaiber, post:1, topic:12039"]
```
> class MyCustomAcceleratorPartitioner(UMAPartitioner):
@property
def target_name(self):
return "my_custom_accelerator"
def _register_patterns(self):
self._register_pattern("conv1d
