Skip to content

Conversation

@mschilli87
Copy link

☑️ Resolves

🖼️ Screenshots

I do not know how to locally build and render the documentation but I only added a few lines to the sample nginx config files that fix an issue I faced after upgrading to NC32.

@mschilli87
Copy link
Author

I will add the sign-off later today. If you auto-block PRs based on linting errors, it would be great to get notified by a comment. I only noticed the failing check because I still had the PR open in a browser tab from yesterday. Also, a PR template pointing with a short checklist of what you expect would be useful.

@mschilli87 mschilli87 force-pushed the fix-nginx-502-root-url-large-response-header branch from e3d04cc to 568c29c Compare October 16, 2025 15:33
@github-actions
Copy link
Contributor

Hello there,
Thank you so much for taking the time and effort to create a pull request to our Nextcloud project.

We hope that the review process is going smooth and is helpful for you. We want to ensure your pull request is reviewed to your satisfaction. If you have a moment, our community management team would very much appreciate your feedback on your experience with this PR review process.

Your feedback is valuable to us as we continuously strive to improve our community developer experience. Please take a moment to complete our short survey by clicking on the following link: https://cloud.nextcloud.com/apps/forms/s/i9Ago4EQRZ7TWxjfmeEpPkf6

Thank you for contributing to Nextcloud and we hope to hear from you soon!

(If you believe you should not receive this message, you can add yourself to the blocklist.)

@mschilli87
Copy link
Author

Is this some sort of cynical joke? Do you really expect me to invest even more time into this PR after it was completely ignored for two weeks straight? I don't care if this ever gets merged. My issues is fixed and I thought this could help others in the same boat to find a solution more quickly. But if I had spend days on fixing a real bug or implementing a new feature, this would be the moment where I probably would decide no to do so again for this project. This is a sure fired way to alienate new contributors.

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.

1 participant