techknowlogick
techknowlogick
This is quite interesting. On one hand user/pass auth for api/git operations are being depreciated, but it does give the idea of otp with scoped tokens 🤔
Couldn't we take the same (or similar approach) to the Label PUT API endpoint (https://try.gitea.io/api/swagger#/issue/issueReplaceLabels) where it accepts an array of labels all in one go? I suspect we could...
> > Couldn't we take the same (or similar approach) to the Label PUT API endpoint (https://try.gitea.io/api/swagger#/issue/issueReplaceLabels) where it accepts an array of labels all in one go? I suspect...
I wonder if this could be achieved with an external renderer via the config so nothing new needs to be added to Gitea
> I think yes, we need to add board events first. I think we could land this PR before board events.
Reopening. While we have instance wide variables, having instance wide secrets would be useful for a specific use case, if the instance is targeted to specific user group then this...
@jbgomond I think we pretty much have the same use case for this.
@theoludwig the branch is created when the first rc is cut.
@tulzke rc0 was released a few hours ago.
As rc0 of 1.22 is now out I will now close/lock this thread. Plans for 1.23 can be listed in the new thread (once it is created)