Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CONTRIBUTING.md: Additional Column Filtering Description in Section 2.2 #3018

Closed
8 tasks done
Sparky-code opened this issue Mar 27, 2022 · 3 comments · Fixed by #3235
Closed
8 tasks done

CONTRIBUTING.md: Additional Column Filtering Description in Section 2.2 #3018

Sparky-code opened this issue Mar 27, 2022 · 3 comments · Fixed by #3235
Assignees
Labels
Complexity: Small Take this type of issues after the successful merge of your second good first issue Feature: Onboarding/Contributing.md role: back end/devOps Tasks for back-end developers role: front end Tasks for front end developers size: 0.5pt Can be done in 3 hours or less Status: Updated No blockers and update is ready for review

Comments

@Sparky-code
Copy link
Member

Sparky-code commented Mar 27, 2022

Overview

As a developer, I would like to clarify the process for choosing new issues to work on, so that higher priority issues can be worked upon first.

Details

Feedback from new members found that practice for choosing most time sensitive issues wasn't entirely clear. This issue aims to reiterate the best practice.

Action Items

  • Add the text specified below to the bottom of section 2.2, but before the current note.

Text:
Note: The Prioritized Backlog column is filtered so the first (top) issue has the highest priority and should be worked on next.

  • Add a line break between the notes.
  • To see the visual changes for the CONTRIBUTING.md and make sure the changes look good:
    • Push the changes to your remote forked repo's topic branch
    • Go to your remote forked repo on GitHub
    • Switch to your topic branch
    • Click on the CONTRIBUTING.md file
    • On the upper right, click on "Display the rendered blob" to see what your changes look like. Here is an image of what
      the "Display the rendered blob" button looks like:
Image of "Display the rendered blob" button

Resources/Instructions

Link to CONTRIBUTING.md section 2.2 - How hack for la organizes issues

Is there a dependency?

No

If Yes, please explain

N/A

@Sparky-code Sparky-code added good first issue Good for newcomers role: front end Tasks for front end developers role: back end/devOps Tasks for back-end developers Feature: Onboarding/Contributing.md size: 0.5pt Can be done in 3 hours or less labels Mar 27, 2022
@github-actions

This comment was marked as resolved.

@Sparky-code Sparky-code changed the title CONTRIBUTING.md: additional column filtering description in sec 2.2 CONTRIBUTING.md: Additional Column Filtering Description in Section 2.2 Mar 27, 2022
@SAUMILDHANKAR SAUMILDHANKAR added Complexity: Small Take this type of issues after the successful merge of your second good first issue Ready for Prioritization and removed good first issue Good for newcomers labels Mar 29, 2022
@ExperimentsInHonesty ExperimentsInHonesty added this to the 08. Team workflow milestone Apr 2, 2022
@SAUMILDHANKAR
Copy link
Member

@Sparky-code Just wanted to share with you some of the formatting edits I made to the issue:

  • Enclosed your note in triple backticks, to create a fenced code block which is easier to copy
  • Added your image to a collapsible dropdown

Thanks again for writing the issue.

@Olanrewaju-Ak Olanrewaju-Ak self-assigned this Jun 8, 2022
@Olanrewaju-Ak
Copy link
Member

ETA: End of the day on 6/10
Availability: 1 hour

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Small Take this type of issues after the successful merge of your second good first issue Feature: Onboarding/Contributing.md role: back end/devOps Tasks for back-end developers role: front end Tasks for front end developers size: 0.5pt Can be done in 3 hours or less Status: Updated No blockers and update is ready for review
Projects
Development

Successfully merging a pull request may close this issue.

4 participants