-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merge v24.3.31 #836
Merge v24.3.31 #836
Conversation
Have you thought about adopting this? It's fine with me, I just want to make sure this is not slipping in unnoticed. Is there a particular reason why you do this? I maintain that no build output shall be part of the repo. The commit adds two new files So in total, I'd like to propose merging ff44267 into |
Guess it's fine. Would help to do our housekeeping.
upps. You are right.
That's fine for me |
c997df5
to
ff44267
Compare
As discussed, I moved the branch tip of this PR to ff44267, which effectively removes the commit I wasn't happy about. |
FYI: I pushed tag v24.3.31 to this repo, pointing to the original upstream commit 1258865. |
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion or issue for related concerns. |
- create webapp