Git and GitHub Workflow | 4th Issue Ticket Task | Git Command Line #14
Replies: 8 comments 9 replies
-
|
Hi @collabo-community/maintainers, i will be participating in this task. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @collabo-community/maintainers, i will be participating in this task. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @collabo-community/maintainers, i will be participating in this task. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @collabo-community/maintainers, i will be participating in this task. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @collabo-community/maintainers |
Beta Was this translation helpful? Give feedback.
-
|
Hi @collabo-community/maintainers, I will be participating in this task. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @collabo-community/maintainers, I will be participating in this task. |
Beta Was this translation helpful? Give feedback.
-
|
Important The name of our community has changed from |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Prerequisite
Ensure that you have completed tasks 1 - 3 of the Git & GitHub Workflow "Good First Issue" Tickets. If you have not done or completed the Git and GitHub tickets, you can find it through the project board here: git and github workflow good first issue tickets
If your pull requests for all the previous tasks have been submitted and approved by a maintainer, you can proceed to do this 4th task.
Helpful resources (git command line)
Issue description
Hurray! 🥳 🎉 Time to move on to another phase.
In this 4th task assignment, you are required to create a file with GitHub markdown content using command line git. Find more information in the expected solution section below.
Expected solution
Tip
Stick to the branch naming convention you have been using. You may also have to first sync your fork's
developbranch with the @collabocate-osc repo'sdevelopbranch, so that your previous tasks' changes that we merged into our develop branch can reflect in your fork's develop branch.gitcollab-cmd-task.mdin the root of the folder that has your GitHub username in it.@gitcollab-learnfolder, in your own newly created file. Once you read the content of the ui-task.md file, you will know what text to change or replace.Additional context
#good-first-issue-supportchannel in our discord community server.Testing checklist
Note (to contributor taking on this task assignment): Add the testing checklist below (without this note) to your pull request when submitting your fix. This will guide (you and) the contributors who will review your fix to know what is important to check or test for.
Replace this inline code block with the link to your approved 3rd task pull requestgitcollab-cmd-task.mdis in the root of the folder that has my GitHub username in it.gitcollab-cmd-task.mdfile uses the content of the ui-task.md file found at the root of the@gitcollab-learnfolder. I have also followed the directions in there to replace text where necessary.Beta Was this translation helpful? Give feedback.
All reactions