Update blank issue form with dependency

[JessicaLucindaCheng]

Dependency

• Create a blank issue form with no dependency #2954

Overview

We want to make the title, description, and format of the Blank Issue form clear that it is for issues with dependencies so that it will be easier and quicker to pick an issue template and write an issue. For this issue, we will update the title and description, and move the dependency section to the top of the form.

Details

The screenshots below were taken by viewing the form on GitHub. (See the last Action Item for detailed instructions on how to do this.)

Click here to see a screenshot of the current form

Click here to see a screenshot of the desired updated form

Action Items

In .github/ISSUE_TEMPLATE/blank-issue-form.yml on your local computer/IDE,

• Move

    - type: dropdown
      id: dependency
      attributes:
        label: Is there a dependency?
        options:
          - "Yes"
          - "No"
      validations:
        required: true
    - type: textarea
      id: dependency-explanation
      attributes:
        label: If Yes, please explain
  

  to right below body:

  name: 'Blank Issue '
  description: 'Standard HackforLA issue template '
  
  body:
  

• Change

  name: 'Blank Issue '
  description: 'Standard HackforLA issue template'
  

  to

  name: 'Blank Issue Form with Dependency'
  description: 'Standard HackforLA issue form with dependency'
  

• To check the form works correctly
  • Push the changes to your remote forked repo's topic branch on GitHub
  • In your remote forked repo on GitHub,
    • You are going to temporarily change the default branch from gh-pages to your topic branch. (See the link in the Resources/Instructions section for more documentation on how to do this.)
    • Then, check you have issues enabled in your forked repo by
      • Going to the Settings tab and then select General in the left menu.
      • On the right side of your screen, scroll until you see the Issues checkbox under the Features section. Make sure the checkbox is checked.
        Click here to see what it looks like when issues are enabled in a repo

        
      • You should now see the Issues tab in your forked repo
    • Now, open an issue within your repo to test out the form you just edited by
      • Going to the Issues tab and clicking the New issue button.
      • Then select Getting Started button for Blank Issue Form with Dependency
      • You should now be able to test out the form and make sure everything functions as expected.
• Once you're done, in your remote forked repo on GitHub, remember to change your default branch back to gh-pages.
• Do items in comment below to finish the issue

Resources/Instructions

• Blank Issue Form: https://github.com/hackforla/website/issues/new?assignees=&labels=&template=blank-issue-form.yml
• Raw view of .github/ISSUE_TEMPLATE/blank-issue-form.yml: https://raw.githubusercontent.com/hackforla/website/gh-pages/.github/ISSUE_TEMPLATE/blank-issue-form.yml
• Blob view of .github/ISSUE_TEMPLATE/blank-issue-form.yml: https://github.com/hackforla/website/blob/gh-pages/.github/ISSUE_TEMPLATE/blank-issue-form.yml
• GitHub's documentation on how to change the default branch

[ExperimentsInHonesty]

The form created can be see here: https://github.com/hackforla/website/issues/new?assignees=&labels=&template=blank-issue-form.yml

[ExperimentsInHonesty]

If we have two versions of the form. One with Dependency and one without, why does it ask you on the dependency one if you have a dependency?

with dependency
without dependency

[ExperimentsInHonesty]

Change the following section items

"Is there a dependency?"

1. Please remove the YES/NO question

"If Yes, please explain"

1. Change the title of text area from If Yes, please explain to Add Dependencies (ideally by issue #)
2. Inside the text area add the default text
   - [ ]

[github-actions]

Hi @Adastros, thank you for taking up this issue! Hfla appreciates you :)

Do let fellow developers know about your:-
i. Availability: (When are you available to work on the issue/answer questions other programmers might have about your issue?)
ii. ETA: (When do you expect this issue to be completed?)

You're awesome!

P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :)

[Adastros]

Availability this week (PST): 9 - 11 PM 29NOV22 , 30NOV22
ETA: 11PM 30NOV22

[ExperimentsInHonesty]

@Adastros I moved this to the in progress column. Please do that in future when you self assign

[Adastros]

Won't be able to finish tonight. Currently asking a dev lead a question I had while working on this issue.

[Adastros]

Hi @ExperimentsInHonesty, I was working on the issue and wanted to get your thoughts on updating the issue template so that it more closely matches the structure of issue #2775 and #3132. Shout out to @JessicaLucindaCheng for helping me out. Below are some images to visualize the changes.

The images with the proposed changes moves the text area title Add Dependencies (ideally by issue #) to the description under the title and uses Dependency as the title instead. The main goal is to structure it similar to issue #2775 and #3132 while making the issue form itself more uniform. It also makes it a bit more convenient having it structured that way so that the user doesn't have to re-edit the issue after submitting it to rename the Dependency section of the issue.

Issue form with previous feedback implemented

Before submitting issue

After submitting issue

Issue form with proposed changes

Before submitting issue

After submitting issue

[ExperimentsInHonesty]

The proposed changes are better. do those

[Adastros]

Availability (PST): 9 - 11 PM 10JAN23
ETA: 11PM 10JAN23

[ExperimentsInHonesty]

good job!