3
1
Fork
You've already forked forgeflow
0

Ping me to get notifications #2

Open
opened 2026年02月11日 17:57:37 +01:00 by defuneste · 5 comments

Just a random test to see if I can generate notifications while pinging myself here: @defuneste

Just a random test to see if I can generate notifications while pinging myself here: @defuneste
Collaborator
Copy link

Ping @defuneste . My code is all up and working in https://codeberg.org/mpadge/mpmisc/src/branch/main/R/github-notifications.R#L16. I alias everything through this script, so i just type cb in my console, and there they are. Then cb 1 to auto-open the first notification.

Ping @defuneste . My code is all up and working in https://codeberg.org/mpadge/mpmisc/src/branch/main/R/github-notifications.R#L16. I alias everything through [this script](https://codeberg.org/mpadge/dotfiles/src/branch/main/system/gh_notifications.bash), so i just type `cb` in my console, and there they are. Then `cb 1` to auto-open the first notification.
Author
Owner
Copy link

I was just trying to get notifications to test the API, pinging myself do not count has a notifications apparently.

It worked when you were pinging me.

I had look at your dotfiles (thanks for sharing I should stole some of your alias!, you have two tree -L 1 :) ).

I will look on how you manage certificates!

I was just trying to get notifications to test the API, pinging myself do not count has a notifications apparently. It worked when you were pinging me. I had look at your dotfiles (thanks for sharing I should stole some of your alias!, you have two `tree -L 1` :) ). I will look on how you manage certificates!
Collaborator
Copy link

Writing this here because it's a thought about notifications. All Forgejo APIs have the same structure, so it'd be super easy and really useful to have a single function which (read a local .config file to know where and then ...) grabbed all notifications from all Forgejo instances, showed them to you, and enabled ready opening of any and all. Like my current function, but without hard-coding URLs, and aggregating notifications across all services.

The minute I had that, I'd switch off email notifications everywhere, which would really help reduce noise. Ping @pat-s, in case you're not yet watching this repo as a whole.

Writing this here because it's a thought about notifications. All Forgejo APIs have the same structure, so it'd be super easy and really useful to have a single function which (read a local `.config` file to know where and then ...) grabbed all notifications from all Forgejo instances, showed them to you, and enabled ready opening of any and all. Like my current function, but without hard-coding URLs, and aggregating notifications across all services. The minute I had that, I'd switch off email notifications everywhere, which would really help reduce noise. Ping @pat-s, in case you're not yet watching this repo as a whole.
Author
Owner
Copy link

I am still thinking, organizing my brain on the problem analysis (sorry I am slow, and at works ...).

On the .config I think it makes sense for beginner to have it but I would like the functionality to be more flexible. IE one function that could set your input to be either a config file (at the profile level or repo level?) or use some ENV variable for example using direnv.

I am still thinking, organizing my brain on the problem analysis (sorry I am slow, and at works ...). On the `.config` I think it makes sense for beginner to have it but I would like the functionality to be more flexible. IE one function that could set your input to be either a config file (at the profile level or repo level?) or use some ENV variable for example using direnv.
Author
Owner
Copy link

I also think that having some higher level function that is returning a data frame (?) with an row per forge/instance would be great:

something like that?

forge instance | notif
forgejo/codeberg | 4
forgejo/my-instance | 2

I also think that having some higher level function that is returning a data frame (?) with an row per forge/instance would be great: something like that? forge instance | notif forgejo/codeberg | 4 forgejo/my-instance | 2
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
r-codeberg/forgeflow#2
Reference in a new issue
r-codeberg/forgeflow
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?