silverwind

Almost, but I would like to also get rid of the PR title modification too. Maybe we can make it work by setting `WORK_IN_PROGRESS_PREFIXES` to the empty string, but I...

For me, icon alone is enough indication. Yes it would require more work because a new DB field needs to be added and a new event type for draft status....

Reason for the change is also that it might be possible that in the future, workflows may be ran when pull request title changes (like spellcheck), and the current "abuse"...

If you want to spellcheck a PR title, you have'd such a hypothetical event like `on: title_change` 😆.

It seems to be possible on GitHub at least: https://github.com/orgs/community/discussions/48695

Maybe duplicate of https://github.com/vitejs/vite/issues/14674, at least I noticed the same bug that vite incorrectly strips import assertions during compilation against a `node18` target. esbuild alone preserves it fine with a...

> BTW, there seems to be no doubt that esbuild is erasing import attributes. That looks like a bug in esbuild. They were initially introduced in node 21 but recently...

I think this is already resolved by config: If you build a browser-targeting library, use the default config. If you build a node-targeting library, remove `browser` from [`resolve.mainFields`](https://vitejs.dev/config/shared-options#resolve-mainfields). I only...

GitHub supports something similar with a `.github` repo [per-org or user](https://docs.github.com/en/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile). I think we could support such special repos too: - `user/.gitea` for user-specific settings/files. - `org/.gitea` for org-specific settings/files....

Does GitHub have this? I think they don't and I think it would be better to just always expand in both directions from UX perspective.