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
If someone install Quarks NuGet package and made useful changes(e.g. bug fix or improvement), what is the process to submit the change back to the repository? I prefer something more simple then fork full repository,clone, change the file(s),commit, push, create pull request.
The text was updated successfully, but these errors were encountered:
You could navigate to the file on GitHub, click the edit button which looks like a pencil, paste your modified code, write a title and description, and then click "Propose file change". This process automatically forks and creates a pull request without you having to clone the repository.
I think it only works for changing a single file though, so you wouldn't be able to increment the version of the package in its associated .nuspec file as well. Unfortunately I don't know of a more simple process than the standard "fork full repository, clone, change the file(s), commit, push, create pull request". It would be heavenly if NuGet supported this as a Visual Studio plugin of some sort, but that's probably just wishful thinking. I suppose there's nothing stopping somebody from inventing a standards-based way of doing this.
If someone install Quarks NuGet package and made useful changes(e.g. bug fix or improvement), what is the process to submit the change back to the repository? I prefer something more simple then fork full repository,clone, change the file(s),commit, push, create pull request.
The text was updated successfully, but these errors were encountered: