img tag refactor in CONTRIBUTING.md Sec 1.3 - first

[roslynwythe]

Prerequisite

1. Be a member of Hack for LA. (There are no fees to join.) If you have not joined yet, please follow the steps on our Getting Started page and attend an onboarding session.
2. Before you claim or start working on an issue, please make sure you have read our How to Contribute to Hack for LA Guide.

Overview

We want to change an img HTML tag ending with a slash (<img.../>) to an img tag without an ending slash (<img...>) so that the codebase is consistent with how we use img HTML tags.

Action Items

• In your local IDE, open the file CONTRIBUTING.md
• In Section 1.3 change

  <img src="https://user-images.githubusercontent.com/21162229/137044762-c80f18e8-b785-48fb-a286-81c1117c0178.jpg" />        

to

  <img src="https://user-images.githubusercontent.com/21162229/137044762-c80f18e8-b785-48fb-a286-81c1117c0178.jpg">      

- [ ] The file may contain more than one instance of an img tag with a closing slash. Only change the single instance specified above. Do not leave any blank spaces before the closing bracket.

• Changes to CONTRIBUTING.md cannot be tested locally, rather they must be tested after pushing the issue branch to your fork of the repository. Push your issue branch in the usual manner, but before creating the Pull Request, check your updates using this test URL (also store the test URL for use in a later step)

https://github.com/[REPLACE WITH GITHUB HANDLE]/website/blob/[REPLACE WITH NAME OF ISSUE BRANCH]/CONTRIBUTING.md

(for example: https://github.com/roslynwythe/website/blob/test-CONTRIB/CONTRIBUTING.md)

• Create a pull request with your changes. In the Pull Request, after the "Why did you make the changes" section, add this line to help reviewers, replacing the text in brackets (and the brackets) with the test URL from the previous Action Item.

For Reviewers: Do not test changes locally, rather test changes at [REPLACE WITH TEST URL]

Merge Team

• After closing this issue, check off the dependency in epic: Refactor img tags in CONTRIBUTING.md to end without a slash #6453. If all dependecies have been completed, close epic: Refactor img tags in CONTRIBUTING.md to end without a slash #6453 and check off its dependency in Rollout Plan: Refactor code with img HTML tags to end without a slash #4362. If all dependencies have been completed in Rollout Plan: Refactor code with img HTML tags to end without a slash #4362, close it.

Resources/Instructions

1. Webpage(s): https://github.com/hackforla/website/blob/gh-pages/CONTRIBUTING.md
2. This issue is part of epic: Refactor img tags in CONTRIBUTING.md to end without a slash #6453

[HackforLABot]

Hello @maadeshsivakumar, we appreciate you taking on issue #7093, however it looks like you've already worked on enough issues of this complexity. Try checking out some of the issues of the next complexity from the Prioritized Backlog :)

We are going to unassign you from this issue so you can take on another issue.

Hfla appreciates you! :)

P.S. There is one exception to this rule/automation, and that is if you were away for a long time, and need to do the issue ladder again. If that is the case, please post the following note on the issue and on your Skills Issue (Pre-work Checklist). A Merge team member will reassign you to this issue, and will help you get assigned to subsequent issues up to medium size.

I am returning after a significant time away, and need to do the issue ladder again. Please assign me back to this issue.

[HackforLABot]

Hi @maadeshsivakumar, HfLA appreciates your interest in this issue, but please note that it is in the "New Issue Approval" column of the Project Board because it has not been finalized, approved, or prioritized, and so it is not ready for assignment. For this reason, you have been unassigned from this issue. Please remember to assign issues only from the "Prioritized Backlog" column.

The only exceptions to this rule are if you are writing an issue and the Draft label is applied, or if you are self-assigning to your "Pre-work Checklist" (the issue includes the Complexity: Prework label).

[daras-cu]

@maadeshsivakumar I see you have an open PR for this issue, but you have already completed a Small issue in the past, #7092. Is there a reason you wanted to work on a second Small issue? It looks like you completed the other one just last month. Please refer to the previous HackforLABot comment. Generally if you receive a comment from the bot and are unassigned from an issue you should double check why before working on it/opening a PR.

[Thinking-Panda]

@maadeshsivakumar In future, Please follow the Skills Issue on the number issues that can be worked on a specific complexity. You can move on to review Complexity: Small issues and the making issues.