Aire-One
Aire-One
Hi @aidinio, sadly most other maintainers are AWOL for some time now... Let's try to ping @awesomeWM/write-access
@mergifyio rebase
> @Aire-One I rebased and force pushed. Still not seeing the CI checks running, but I wonder if that's because I'm a new contributor and need the approval for workflows....
I'll not be able to put time on this this week. So any help is welcome.
@denisoster this is a different problem. It is already reported to lgi at https://github.com/lgi-devs/lgi/issues/346 and should be fixed by upstream with https://gitlab.gnome.org/GNOME/glib/-/merge_requests/4792. As explained to you in https://github.com/awesomeWM/awesome/pull/4022#issuecomment-3375727676, you can...
The symptoms sound like the program "remembers" the last position when closed and restore itself to it at next opening. You should be able to force ignore this behavior with...
I don't particularly like that. I noticed you squashed recent PRs, but do we absolutely need to force it every time? For PR with unclean commits, we can do it...
> just statistically amount of PRs which must be squashed is outstandingly bigger than those which need to be merged with retaining sub-commits Yeah, I guess :shrug:
@actionless I don't have the access right to force merge when necessary conditions (2 approving reviews) aren't meet, tho...