Skip to content
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

fix: Fix content type to application/yaml #27

Merged
merged 1 commit into from
Dec 9, 2024
Merged

Conversation

raeperd
Copy link
Owner

@raeperd raeperd commented Dec 9, 2024

@raeperd raeperd self-assigned this Dec 9, 2024
@raeperd raeperd merged commit 8bbd419 into main Dec 9, 2024
4 checks passed
@raeperd raeperd deleted the fix-content-type branch December 9, 2024 14:18
@ccoVeille
Copy link
Contributor

You could have pushed your commit in my branch, no?

@raeperd
Copy link
Owner Author

raeperd commented Dec 9, 2024

I couldn't. maybe allow edit was needed?

@ccoVeille
Copy link
Contributor

I think it's a limitation of something I tried.

I moved my forks in a dedicated organization

https://github.com/ccoveille-forks

I didn't notice until yet it may have consequence when I open a PR.

Doing it from an organization and from a user might differ slightly.

If I don't grant you to push on my fork in my organization, you might not be able to do it.

I'll have to dig further.

I did all that with a script. I might have to grant the users one by one.

Which would be easy for you on this project. But it could become a nightmare on project with multiple maintainers...

I'll have to check and reconsider

@ccoVeille
Copy link
Contributor

Here is my script

ccoVeille/github-forks-sanitizer#1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants