Tutorial:Contributing Code - Revision history

Imbion: Imbion moved page Contributing Code to Tutorial:Contributing Code

2025-10-16T15:46:38Z

Imbion moved page Contributing Code to Tutorial:Contributing Code

← Older revision	Revision as of 15:46, 16 October 2025
(No difference)

IDK: PR images

2023-06-06T04:46:44Z

PR images

← Older revision		Revision as of 04:46, 6 June 2023
Line 12:		Line 12:
	Then, you will need to fork the repo you are making changes to from github's UI:		Then, you will need to fork the repo you are making changes to from github's UI:

	~~<Image of the fork button on github's UI>~~		[[File:PR_Create_Fork.png\|frameless]]

	In this case, we are forking RogueEssence, but if your changes have affected other repos such as PMDODump or PMDC, you will need to fork them separately as well.		In this case, we are forking RogueEssence, but if your changes have affected other repos such as PMDODump or PMDC, you will need to fork them separately as well.
Line 30:		Line 30:
	It should now appear as a branch in your repository.		It should now appear as a branch in your repository.

	~~<Image of the branch>~~		[[File:PR_Branch.png\|frameless]]

	Next, create a pull request from this branch. Github makes it easy with a single button:		Next, create a pull request from this branch. Github makes it easy with a single button:

	~~<Image of~~ the ~~PullRequest button>~~		[[File:PR_Create_PullRequest.png\|frameless]]

			You will be taken to a UI where you can compare your branch's difference with the original repo, as well as add comments on what you changed.

			[[File:PR_Comparing.png\|frameless]]

	The pull request is now added. Now you will just need to wait until the code gets reviewed, and the branch will either be merged into the main repo or you will be asked for changes.		The pull request is now added. Now you will just need to wait until the code gets reviewed, and the branch will either be merged into the main repo or you will be asked for changes.

			[[File:PR_Create_Complete.png\|frameless]]

	[[Category: Engine]]		[[Category: Engine]]

IDK at 03:22, 5 May 2023

2023-05-05T03:22:02Z

← Older revision		Revision as of 03:22, 5 May 2023
Line 37:		Line 37:

	The pull request is now added. Now you will just need to wait until the code gets reviewed, and the branch will either be merged into the main repo or you will be asked for changes.		The pull request is now added. Now you will just need to wait until the code gets reviewed, and the branch will either be merged into the main repo or you will be asked for changes.

			[[Category: Engine]]

IDK: created

2023-05-05T03:21:38Z

created

@@ Line 1: / Line 1: @@
 PMDO is open source with the MIT license.  It means that anyone is allowed to use, redistribute, and modify the software among other things.  When you push to github you provide code under the same license.
-To contribute to PMDO, you will need to create a Pull Request of your code.  In order to do that, you need to push a branch to a fork of the original repo.
+To contribute to PMDO, you will need to create a Pull Request of your code.  In order to do that, you need to push a branch to a fork of the original repo.  And in order to do that, you need to have a branch, and have a fork.
-First, if you have already made edits to PMDO on your local copy by following the [[Debugging_PMDO| Debugging tutorial]]
+First, let's create our own branch.  If you have already made edits to PMDO on your local copy by following the [[Debugging_PMDO| Debugging tutorial]], you will need to create a new branch of your work and commit to it.
 <pre>
 </pre>

IDK: intro

2023-05-05T03:06:01Z

intro

New page

PMDO is open source with the MIT license. It means that anyone is allowed to use, redistribute, and modify the software among other things. When you push to github you provide code under the same license.

To contribute to PMDO, you will need to create a Pull Request of your code. In order to do that, you need to push a branch to a fork of the original repo.

First, if you have already made edits to PMDO on your local copy by following the [[Debugging_PMDO| Debugging tutorial]]
<pre>
</pre>