qwerty287
qwerty287
Not really. The first issue is Node-Sass, if I try to replace it with Dart-Sass it fails when trying to build `node-gyp`. I was able to successfully run `npm install...
@rvishnyakov It would be very cool if you could look at this PR (it changes only one line, reviewing should be easy).
I'm not sure, but maybe this fixes itself for pull requests after a while... One where I can reproduce it is https://github.com/woodpecker-ci/woodpecker/pull/861.
@maniac103 > Are you referring to this feature? I'd think it's this: https://docs.github.com/en/discussions But it looks like there is currently only a GraphQL API for this (https://docs.github.com/en/graphql/guides/using-the-graphql-api-for-discussions)
Why are the user overview (#741) and the branches list only available if I'm logged in, even if the repo is public? Is there any reason for this?
I didn't think about this yet 😂 Both options are possible, but handling both is probably better.
We have to look at forges that are not Github, Gitlab and Gitea in general a bit more...
Maybe we could add some more complex options here: - **first time contributors**: require approval for users contributing the first time - **once per PR**: once a PR is approved...
Actually, if you have repo write permissions on the corresponding forge (Gitea, GitLab, GitHub), this should be working. You can use Settings -> Secrets and add one. Doesn't this work...
It is part of 0.15.1 and previous versions as well. But there is the issue: the users need repo **admin** permissions on Github, just write is not enough. That's something...