Skip to content

ProcessingAnIssue.md

Latest commit

 

History

History
59 lines (38 loc) · 3.32 KB

ProcessingAnIssue.md

File metadata and controls

59 lines (38 loc) · 3.32 KB

Processing an Issue

In preparation for processing an Issue, you have to assure that you are working based on the correct and up-to-date develop branch.

  • For changing into the local develop branch, you have to open the list of branches ...
    processIssuePicture31

  • ... and chose the develop branch from the list.
    processIssuePicture32

  • Now, as the develop branch is indicated in the lower left corner...
    processIssuePicture32

  • ... you can assure your local data being in synch with the remote repository by clicking on the round arrow.
    processIssuePicture34

Starting to actually work on the Issue.

  • You have to click on the GitHub symbol to the left of the VSCode window.
    processIssuePicture1

  • Expand the list of Issues by clicking the arrow besides "ISSUES".
    processIssuePicture2

  • Update the list of Issues by clicking the circle arrow.
    processIssuePicture3

  • Expand the repository, which shall be processed.
    processIssuePicture4

  • If the Issue has been assigned to you, you will find it in "My Issues".
    Otherwise, check "Created Issues", if you created the Issue by yourself, but forgot to assign it to yourself.
    processIssuePicture5

  • Find the Issue, which you would like to process, and click the arrow to the right for starting to work on the Issue.
    processIssuePicture6

  • Now, the Issue is marked to be in grogress.
    processIssuePicture7

Attention! During the latest step, a new branch has been created locally and VSCode automatically switched its view into this branch.

processIssuePicture8

This step would not succeed, if you would neither be owner nor Contributor to the addressed repository.
In such case you would be informed about not having permission for pushing into the addressed repository and you would be asked, whether you would like to fork (copy) the addressed repository into your own GitHub account.
If you would confirm forking, you would proceed according to the Forking Workflow, which is absolutely fine, too.

  • It is recommended to click the cloud symbol for publishing the new branch on the remote GitHub for indicating that work on this Issue is on-going.
    processIssuePicture9

  • Click on the Explorer symbol for starting to be productive in the new branch.
    processIssuePicture10

Of course, your actual doing should now exclusively relate to the chosen Issue until you committed into the branch, which has been created for that purpose.

See Creating a Commit and Creating a Merge Request for consequent steps.

<- Back to Documenting an Issuee - - - Up to Preparing for Specifying Applications - - - Ahead to Creating a Commit ->