You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 the ImportAll and ExportAll functions. 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.
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".
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
<#253 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACH6DINSF6ZKDRQMXJRNMTZ6WJ57AVCNFSM6AAAAABLJPUQZGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJTGI3TQOBWGY>
.
You are receiving this because you commented.Message ID:
***@***.***>
Activity
kumaran-14 commentedon Nov 26, 2019
I would like to start working on this. Any tips on how to proceed with this?
MichaelMure commentedon Nov 26, 2019
Hey, thanks for looking into that. Here is the rundown (once #263 is merged):
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.kumaran-14 commentedon Nov 28, 2019
Thanks for the heads up. I'm trying the load the default bridge as you said.
bqv commentedon Mar 28, 2022
@kumaran-14 did you get anywhere?
hchev001 commentedon Jan 8, 2023
@bqv did you get anywhere? considering you never got a reply
bqv commentedon Jan 8, 2023
nope
github-actions commentedon Jul 23, 2024
This bot triages untriaged issues and PRs according to the following rules:
lifecycle/stalelabel is appliedlifecycle/stalewas applied, the issue is closedTo remove the stale status, you can:
lifecycle/stalelabelbqv commentedon Jul 24, 2024
bots. 😩
sudoforge commentedon Aug 3, 2024
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".
github-actions commentedon Nov 3, 2024
This bot triages issues in order to help the maintainers identify what
needs attention, according to the following lifecycle rules:
lifecycle/staleis appliedlifecycle/stalewas applied,lifecycle/rottenis appliedThis bot will not automatically close stale issues.
To remove the stale status, you can:
To avoid automatic lifecycle management of this issue, add
lifecycle/frozen.MichaelMure commentedon Nov 3, 2024
mohammadazeemwani commentedon Jan 27, 2026
Yup not stale.
I wonder what are the Push and Pull in the termUI for ?
Issues only reflect when I do
git bug bridge pushoutside of termui ?Am I missing anything.