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

Convert Mobile_responsiveness Template to Github Form Issue #2290

Closed
3 tasks done
adrian-zaragoza opened this issue Sep 21, 2021 · 1 comment · Fixed by #3014
Closed
3 tasks done

Convert Mobile_responsiveness Template to Github Form Issue #2290

adrian-zaragoza opened this issue Sep 21, 2021 · 1 comment · Fixed by #3014
Assignees
Labels
Complexity: Small Take this type of issues after the successful merge of your second good first issue Feature: Board/GitHub Maintenance Project board maintenance that we have to do repeatedly p-Feature: Mobile role: back end/devOps Tasks for back-end developers size: missing Status: Updated No blockers and update is ready for review

Comments

@adrian-zaragoza
Copy link
Member

adrian-zaragoza commented Sep 21, 2021

Overview

As an issue creator, we want to implement issue templates for issue creation to streamline and simplify the process. The current issue forms require the person to replace the text, and is less user-friendly compared to GitHub Form issues.

Action Items

  • Create a Mobile_responsiveness.yml file in this folder
  • Add the code below to the file
name: 'Responsiveness on mobile '
description: 'Standard HackforLA issue template '
title: 'Mobile Responsiveness on [name of the page] : [quick recap of the bug here]'
labels: ['role: design']
# assignees:

body:
  - type: textarea
    id: overview
    attributes:
      label: Overview
      description: |
        We need to check the mobile version of every pages on the website so that we correct any bug that is appearing on mobile.
        1. Explain the bug that you have observed
        2. Put a screenshot of the bug: you can use the following template to create a drop down image
      value: |
        <details>
        <summary>TITLE IMAGE </summary>
        ![image](https://user-images.githubusercontent.com/77212035/134111368-bc5dfa08-0dd3-47be-a0e2-a60c6a362bf7.png)
        </details>
    validations:
      required: true
  - type: markdown
    attributes:
      value: "## Action Items"
  - type: checkboxes
    id: action-design
    attributes:
      label: "Design:"
      options:
        - label: "Check the mobile responsiveness of this page (use your mobile to do it ;) )"
        - label: "If there is any bug/any inconsistency or problem, however small or large, edit this issue and list the bug with screenshots in the Overview section above. _You have more than one bug? duplicate this issue and create one issue per bug. "
        - label: "List all the changes to implement to correct the bug (eg: resizing..) in the development action items below. (don't hesitate to create 1 checkbox for each changes)"
        - label: "Put the issue(s) in the review column to check the feasibility with the devs. "
  - type: textarea
    id: action-development
    attributes:
      label: Development
      value: |
        - [ ] Implement the following changes : '_list your changes here_ '
        - [ ] Ensure that the correction doesn't break any other pages that is connected to the one your changing. For that, check  [the sitemap](https://www.hackforla.org/sitemap.xml)
  - type: textarea
    id: resources-instructions
    attributes:
      label: Resources/Instructions
      description: Provide links to the figma file (if there is one), and to the page where the bug is observed.
    validations:
      required: true
  • Delete Mobile_responsiveness.md

Resources/Instructions

Before Changes Screenshot
After Changes Screenshot

Github Forms Issue Reading
Github Forms Issue Reading Pt 2
#2128

@github-actions github-actions bot added Feature Missing This label means that the issue needs to be linked to a precise feature label. role missing size: missing labels Sep 21, 2021
@adrian-zaragoza adrian-zaragoza added Feature: Board/GitHub Maintenance Project board maintenance that we have to do repeatedly role: front end Tasks for front end developers good first issue Good for newcomers and removed Feature Missing This label means that the issue needs to be linked to a precise feature label. role missing size: missing labels Sep 21, 2021
@ExperimentsInHonesty ExperimentsInHonesty added the Dependency An issue is blocking the completion or starting of another issue label Oct 4, 2021
@ExperimentsInHonesty ExperimentsInHonesty added this to the 08. Team workflow milestone Oct 4, 2021
@ExperimentsInHonesty ExperimentsInHonesty added Complexity: Small Take this type of issues after the successful merge of your second good first issue Size: Good second issue role: back end/devOps Tasks for back-end developers and removed Ready for Prioritization Dependency An issue is blocking the completion or starting of another issue good first issue Good for newcomers role: front end Tasks for front end developers labels Oct 4, 2021
@harshitasao harshitasao self-assigned this Mar 25, 2022
@harshitasao
Copy link
Member

Availability : Flexible
My estimated ETA : 26/03/2022

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: Board/GitHub Maintenance Project board maintenance that we have to do repeatedly p-Feature: Mobile role: back end/devOps Tasks for back-end developers size: missing Status: Updated No blockers and update is ready for review
Projects
Development

Successfully merging a pull request may close this issue.

6 participants