It should be possible to push/pull the configured bridges from the termui interface. Or at least Ctrl-Z to background the termui.
It's the two things I use in my workflow: web and termui.
feat: termui push/pull bridge
Labels: area/ui/terminal kind/feature lifecycle/stale priority/awaiting-more-evidence triage/needs-information
Timeline
I would like to start working on this. Any tips on how to proceed with this?
Hey, thanks for looking into that. Here is the rundown (once #263 is merged):
- in the termui, look at how the normal push/pull is done, you will have to do something quite similar
- for now, only wire the default bridge, we will deal with multiple bridges later
- once you have loaded the default bridge with
bridge.DefaultBridge(...), you will get theImportAllandExportAllfunctions. Those functions will return you a channel of events. You'll need to filter and format those events into something that make sense for the termui. Look at the CLI commands for an example.
Thanks for the heads up. I'm trying the load the default bridge as you said.
@kumaran-14 did you get anywhere?
@bqv did you get anywhere? considering you never got a reply
nope
This bot triages untriaged issues and PRs according to the following rules:
- After 90 days of inactivity, the
lifecycle/stalelabel is applied - After 30 days of inactivity since
lifecycle/stalewas applied, the issue is closed
To remove the stale status, you can:
- Remove the
lifecycle/stalelabel - Comment on this issue
bots. 😩
sudoforge removed label Easy pick
sudoforge removed label enhancement
sudoforge added label kind/feature
sudoforge added label priority/awaiting-more-evidence
sudoforge added label triage/needs-information
sudoforge commented
bots. 😩
hey @bqv , thanks for bringing this up.
I initially added the stale configuration as a way to identify things that have been sitting for a long time (there was little to no activity in this repository for two years, after all; and before that, there was about a two year gap between releases as well).
The workflow has since been refactored such that issues and pull requests will never be closed. This better reflects the intent: that "staleness" is really just an indicator for the maintainers, as a way to say "hey, pay attention to this and take action on it".
This bot triages issues in order to help the maintainers identify what needs attention, according to the following lifecycle rules:
- After 90 days of inactivity,
lifecycle/staleis applied - After 90 days of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied
This bot will not automatically close stale issues.
To remove the stale status, you can:
- Remove the stale label from this issue
- Comment on this issue
- Close this issue
- Offer to help out with triaging
To avoid automatic lifecycle management of this issue, add
lifecycle/frozen.
Not stale
On Sun, Nov 3, 2024, 4:28 AM github-actions[bot] @.***> wrote:
This bot triages issues in order to help the maintainers identify what needs attention, according to the following lifecycle rules:
- After 90 days of inactivity, lifecycle/stale is applied
- After 90 days of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
This bot will not automatically close stale issues.
To remove the stale status, you can:
- Remove the stale label from this issue
- Comment on this issue
- Close this issue
- Offer to help out with triaging
To avoid automatic lifecycle management of this issue, add lifecycle/frozen.
— Reply to this email directly, view it on GitHub https://github.com/git-bug/git-bug/issues/253#issuecomment-2453278866, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACH6DINSF6ZKDRQMXJRNMTZ6WJ57AVCNFSM6AAAAABLJPUQZGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJTGI3TQOBWGY . You are receiving this because you commented.Message ID: @.***>