- Pokémon Essentials Version
- Non-applicable
Small tutorial for absolute Git beginners who want to start contributing to Essentials.
First let's find out what is on the Potential Projects and see what can be contributed based on this Google Docs made by Maruno. (Note: New Gen stuff is always a potential project)
https://docs.google.com/document/d/1nsa-WLm7ZViP6XOicO0C4yu4nz-2WYkPMRtXC30A1Eo/edit
Let's access Essentials GitHub in "dev" branch.
https://github.com/Maruno17/pokemon-essentials/tree/dev
Understanding the "master" and "dev" branch in Essentials GitHub.
(Note: "pull requests" are how we will make contributions to Essentials GitHub)
When opening Essentials GitHub you will be redirected to the "master" branch which currently will only have changes made up to the latest v20.1 Hotfixes Plugin - Aug 10, 2022.
But if we move to the "dev" branch we can see that the last update was yesterday, that's because in the dev branch Maruno is preparing v21, and it is exactly in this branch that we will be making "pull requests".
We can start creating a "Fork".
In your newly created "Fork" you select "dev" branch.
And select "Create codespace on dev". (Basically Visual Studio Code on the cloud)
(Note: You can access the "codespace" again if you need to exit and it will save your changes to the cloud)
Make your changes. (Note: without creating the Audio/Graphics/Plugins folder, just Ruby code or PBS data and after testing your changes locally)
After making any changes, it will appear in "SOURCE CONTROL", when finished, write a commit name where it says "my commit" and select "Commit". (Note: You can make multiple "commits" before or after doing a "pull request")
Select "Yes".
Select "Sync Changes".
Now it will show "Compare & pull request" in your "Fork".
But if a long time has passed it will not appear and you will need to do it like this.
You will compare it to the Maruno repository's "base: dev" as the "base repository" and your "compare: dev" branch as the "head repository".
You can write a title that makes sense based on your changes and provide detailed comments about what you are implementing and select "Create pull request".
Your "pull request" will now be waiting for Maruno's review, he can request some changes, accept it directly or reject it.
Congrats you made your first "pull request"!!
First let's find out what is on the Potential Projects and see what can be contributed based on this Google Docs made by Maruno. (Note: New Gen stuff is always a potential project)
https://docs.google.com/document/d/1nsa-WLm7ZViP6XOicO0C4yu4nz-2WYkPMRtXC30A1Eo/edit
Let's access Essentials GitHub in "dev" branch.
https://github.com/Maruno17/pokemon-essentials/tree/dev
Understanding the "master" and "dev" branch in Essentials GitHub.
(Note: "pull requests" are how we will make contributions to Essentials GitHub)
When opening Essentials GitHub you will be redirected to the "master" branch which currently will only have changes made up to the latest v20.1 Hotfixes Plugin - Aug 10, 2022.
But if we move to the "dev" branch we can see that the last update was yesterday, that's because in the dev branch Maruno is preparing v21, and it is exactly in this branch that we will be making "pull requests".
We can start creating a "Fork".
In your newly created "Fork" you select "dev" branch.
And select "Create codespace on dev". (Basically Visual Studio Code on the cloud)
(Note: You can access the "codespace" again if you need to exit and it will save your changes to the cloud)
Make your changes. (Note: without creating the Audio/Graphics/Plugins folder, just Ruby code or PBS data and after testing your changes locally)
After making any changes, it will appear in "SOURCE CONTROL", when finished, write a commit name where it says "my commit" and select "Commit". (Note: You can make multiple "commits" before or after doing a "pull request")
Select "Yes".
Select "Sync Changes".
Now it will show "Compare & pull request" in your "Fork".
But if a long time has passed it will not appear and you will need to do it like this.
You will compare it to the Maruno repository's "base: dev" as the "base repository" and your "compare: dev" branch as the "head repository".
You can write a title that makes sense based on your changes and provide detailed comments about what you are implementing and select "Create pull request".
Your "pull request" will now be waiting for Maruno's review, he can request some changes, accept it directly or reject it.
Congrats you made your first "pull request"!!
- Credits
- Maruno
