- Issue created by @swirt
- π¦πΉAustria klausi π¦πΉ Vienna
Thanks for the suggestion!
Can you describe in the issue summary why we would need this for Coder? For checking changes of a Coder merge request I can checkout Coder locally and run it? Or what am I missing here, how would you apply Tugboat to test a merge request?
Another restriction is that we develop Coder at Github https://github.com/pfrenssen/coder . So we don't use/run drupal.org merge requests.
- πΊπΈUnited States swirt Florida
Good question klausi
I got a little carried away adding this to all modules that CivicActions has ever supported. I was a bit on auto-pilot after doing a bunch of them and did this without thinking about coder's unique case of not actually being a module. So at this time it is probably not of any use to coder maintainers. However, I do know it is on the D.o / Tugboat integration roadmap to support terminal access to the tugboat instance, and in that case it might be more useful for coder maintainers and contributors.
This issue could either be
- parked until that feature becomes available
- merged without harm but no immediate usefulness to coder
- closed as not needed
- π¦πΉAustria klausi π¦πΉ Vienna
I see, thanks for clarifying! Then I will close this for now and we can reopen or make a new issue in the future if this becomes relevant.