You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 18, 2021. It is now read-only.
As a maintainer of a repository, I'd love to accept easy pull requests via website editing for documentation, since that is easy to verify just by looking at it.
However, code changes (especially C++ and JavaScript) frequently leads to syntax errors and broken tests, because it's very difficult to verify that code is correct just by looking at it in the editor.
I'd love to be able to disable the edit-in-place features for joyent/node. As a bonus, it'd be nice if I could enable it only for the doc/ folder of the repo, but disable it for the rest of the repository. But for us, disabling it on the src and lib folders would be worth disabling it for the entire repository if that's easier to do.
The text was updated successfully, but these errors were encountered:
I'm also thinking about the nodejs/node repo :)
I thought of this because once I got write access, I can't use the "create a branch on my own fork" and end up with a branch on the main repo, which is not the intended outcome.
As a maintainer of a repository, I'd love to accept easy pull requests via website editing for documentation, since that is easy to verify just by looking at it.
However, code changes (especially C++ and JavaScript) frequently leads to syntax errors and broken tests, because it's very difficult to verify that code is correct just by looking at it in the editor.
I'd love to be able to disable the edit-in-place features for joyent/node. As a bonus, it'd be nice if I could enable it only for the doc/ folder of the repo, but disable it for the rest of the repository. But for us, disabling it on the src and lib folders would be worth disabling it for the entire repository if that's easier to do.
The text was updated successfully, but these errors were encountered: