Details
-
Type: Task
-
Status: Pull Request Submitted (View Workflow)
-
Priority: Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:
-
Story Points:2
-
Epic Link:
-
Sprint:Fall 2018 Sprint 5, Winter 2018 Sprint 1, Winter 2018 Sprint 3, Spring 2019 Sprint 1, Spring 2019 Sprint 2, Summer 2019 Sprint 7, Summer 2019 Sprint 8, Summer 2019 Sprint 9, Fall 5 : 14 Oct to 25 Oct, Fall 6 : 28 Oct to 8 Nov, Fall 7 : 11 Nov to 22 Nov, Fall 8 : 25 Nov to 6 Dec, Spring 9 : 25 May to 8 Jun, Summer 3: 6 Jul - 17 Jul, Summer 4: 14 Jul - 28 Jul, Summer 6: 17 Aug - 28 Aug, Summer 7: 31 Aug - 11 Sep, Fall 3: Oct 12 - Oct 23, Winter 5 Feb 22 - Mar 5, Winter 6 Mar 8 - Mar 19, Spring 4 2021 May 3 - May 14, Spring 5 2021 May 17 - May 28, Summer 2 2023 May 29, Fall 4 2023 Oct 16, Spring 2, Spring 5, Fall 1, Fall 5
Description
The main goal of this ticket/issue is for you to practice the IGB workflow using Jira.
You'll make a small change to the code base, test it, and then move your ticket forward in the board.
To start, download and run IGB. Then, Select Help > About Integrated Genome Browser.
Note there is a list of contributors. For this task, add your name to the list.
Note:
- Assign this issue to yourself, and move it into the current spring to the "In Progress" lane.
- Read and review the comments and previous work done by others. Review the comments and history for the linked issues, as well.
- Work on editing the proper section of code and adding your name to the credits. Use the IGB fork-and-branch workflow.
- Once you've completed the code changes, run a successful pipeline, and commented a link to your branch, moved this ticket to the "Needs first level review" column, and unassign yourself.
Reminders and tips:
- Make sure your installer has built (as seen in your downloads section). Whoever does the functional review will download and run your installer.
- Make sure you add a link to your fork and branch as a comment to the issue. Whoever does code review will need the link to find your fork and view your code.
- Use correct voice and format for commit messages.
Reviewers:
- Check that the installer has built.
- Check that all commit messages contain the ticket number.
- Check that commit messages are imperative voice, present tense.
- Check that the ticket contains a link to the fork.
- Check that only one line of code is changed (no whitespace edits).
Attachments
Issue Links
- blocks
-
IGBF-2125 On-boarding: Step 5 - Learn OSGi basics from OSGi in Action text
- In Progress
- is blocked by
-
IGBF-1764 On-boarding: Step 2 - fork IGB team repository and set up bitbucket pipelines to build installers
- Closed
-
IGBF-1573 On-boarding: Step 3 - get familiar with IGB workflow and git
- Closed
- is cloned by
-
IGBF-2412 CLONE - On-boarding: Step 4 - add your name to Credits
- Closed
- relates to
-
IGBF-1572 Add your name to Credits
- Closed
-
IGBF-1738 Add your name to Credits
- Closed
-
IGBF-1347 Add your name to credits in About IGB window
- Closed
Please review my changes:
https://bitbucket.org/pawanbole/integrated-genome-browser-pawan/branch/IGBF-1464#diff