Skip to content

Commit 1728c79

Browse files
author
Kacy Luzzardi
committed
Add upstream & upstreamfr commands
1 parent 56443c4 commit 1728c79

2 files changed

Lines changed: 68 additions & 0 deletions

File tree

src/commandes/upstream.js

Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
module.exports = {
2+
"title": "Update launcher from upstream",
3+
"description": "Here's a quick guide to fetch the latest changes from the original repository.",
4+
"fields": [
5+
{
6+
"title": "1.",
7+
"description": "First, you'll need to add the original repo as a remote origin. If you already done so, you can skip this step.\n`git remote add upstream git@github.com:dscalzi/HeliosLauncher.git`"
8+
},
9+
{
10+
"title": "2.",
11+
"description": "Ensure your git tree is clean, meaning every changes you made have been committed and pushed to your repo."
12+
},
13+
{
14+
"title": "3.",
15+
"description": "You may now fetch the history from the original repository using `git fetch upstream`"
16+
},
17+
{
18+
"title": "4.",
19+
"description": "You can now update your local branch with `git checkout master` then `git merge upstream/master`"
20+
},
21+
{
22+
"title": "5.",
23+
"description": "Fix any merge conflict you may have. Here's an article from Github that may help you : [Resolving a merge conflict using the command line](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line)"
24+
},
25+
{
26+
"title": "6.",
27+
"description": "Commit and push your changes"
28+
},
29+
{
30+
"title": "7.",
31+
"description": "Your repo is up to date! You can now push an update to your players."
32+
}
33+
]
34+
}

src/commandes/upstreamfr.js

Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
module.exports = {
2+
"title": "Mettre à jour le launcher",
3+
"description": "Comment mettre à jour le launcher avec les modifications du repo originel ?",
4+
"fields": [
5+
{
6+
"title": "1.",
7+
"description": "Premièrement, vous devez ajouter le repo originel en tant qu'origine distance. Si vous l'avez déjà fait, passez cette étape.\n`git remote add upstream git@github.com:dscalzi/HeliosLauncher.git`"
8+
},
9+
{
10+
"title": "2.",
11+
"description": "Assurez-vous que votre branche locale est propre, autrement dit, que toutes vos modifications ont bien été \"commit\" et poussées."
12+
},
13+
{
14+
"title": "3.",
15+
"description": "Vous pouvez maintenant récupérer l'historique du repo originel avec `git fetch upstream`"
16+
},
17+
{
18+
"title": "4.",
19+
"description": "Procédez à la mise à jour de votre branche locale à l'aide de `git checkout master` puis `git merge upstream/master`"
20+
},
21+
{
22+
"title": "5.",
23+
"description": "Réparez les potentils conflits de fusion que vous pourriez avoir. Voilà un article de GitHub pour vous aider : [Résolution d’un conflit de fusion en utilisant la ligne de commande](https://docs.github.com/fr/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line)"
24+
},
25+
{
26+
"title": "6.",
27+
"description": "Faîtes un \"commit\" et poussez vos changements."
28+
},
29+
{
30+
"title": "7.",
31+
"description": "Votre repo est maintenant à jour ! Vous pouvez publier une mise à jour à vos joueurs."
32+
}
33+
]
34+
}

0 commit comments

Comments
 (0)