What is proper etiquette and recommended GitHub workflow for simultaneously contributing to and diverging from upstream repo?
I’m new to GitHub and VCS in general. I’ve been programming in various languages for years, but I’ve always worked solo on custom projects (no public releases). I recently started using a jQuery UI widget I downloaded from GitHub in a project I am working on. The repo is no longer maintained by the original author. Another fork has incorporated some of the original pull requests. This is the one I forked from.
What is the etiquette of renaming an open source fork?
I want to fork on Github the TestNG java testing framework (Apache 2 license) so I can add/change some minor things to suit my needs.
What is proper etiquette for releasing a complete rewrite of an existing project?
I’m new to the opensource world. The project I’m working on resides on Github. (Just for reference) The project I’m working on is a plug-in for the Plex Media Server. I plan to submit my plug-in to Plex so that it will be included in their “app store”. Now to my question.
Etiquette for editing someone’s pull request
I own a repository on GitHub to which someone sent a pull request with one single commit. I only want to implement his solution partially, and use about half of the code changes the user made. What should I do in this situation?
Etiquette for editing someone’s pull request
I own a repository on GitHub to which someone sent a pull request with one single commit. I only want to implement his solution partially, and use about half of the code changes the user made. What should I do in this situation?
Etiquette for editing someone’s pull request
I own a repository on GitHub to which someone sent a pull request with one single commit. I only want to implement his solution partially, and use about half of the code changes the user made. What should I do in this situation?
GitHub etiquette for duplicating a repo to change functionality
I’ve found a GitHub project I’d like to add some features to. After contacting the maintainer, the changes aren’t in line with the direction he’s going but he’s interested to see what I do with it. What is the GitHub etiquette for using one repo as a base for another project that almost certainly won’t ever be merged back into the original?
GitHub etiquette for duplicating a repo to change functionality
I’ve found a GitHub project I’d like to add some features to. After contacting the maintainer, the changes aren’t in line with the direction he’s going but he’s interested to see what I do with it. What is the GitHub etiquette for using one repo as a base for another project that almost certainly won’t ever be merged back into the original?
GitHub etiquette for duplicating a repo to change functionality
I’ve found a GitHub project I’d like to add some features to. After contacting the maintainer, the changes aren’t in line with the direction he’s going but he’s interested to see what I do with it. What is the GitHub etiquette for using one repo as a base for another project that almost certainly won’t ever be merged back into the original?
GitHub etiquette for duplicating a repo to change functionality
I’ve found a GitHub project I’d like to add some features to. After contacting the maintainer, the changes aren’t in line with the direction he’s going but he’s interested to see what I do with it. What is the GitHub etiquette for using one repo as a base for another project that almost certainly won’t ever be merged back into the original?