Skip to content

Conversation

@sigmaSd
Copy link
Collaborator

@sigmaSd sigmaSd commented May 10, 2025

No description provided.

@sigmaSd sigmaSd requested a review from a team as a code owner May 10, 2025 01:14
@sigmaSd
Copy link
Collaborator Author

sigmaSd commented May 10, 2025

Its ok If I push changes directly or should I open a pr each time ?

@bbhtt
Copy link
Collaborator

bbhtt commented May 10, 2025

It has to go through a PR, pushing directly is blocked via branch protection. If this had only changes in deno/** you will be able to merge it on your own.

@bbhtt
Copy link
Collaborator

bbhtt commented May 10, 2025

Also make sure to prefix the commits with deno: I will rewrite it for now

@bbhtt bbhtt merged commit 24216a1 into flatpak:master May 10, 2025
2 checks passed
@bbhtt
Copy link
Collaborator

bbhtt commented May 10, 2025

I assigned the deno workflows to you too #464

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants