chore: add catalog info

[ichintanjoshi]

Description

• added catalog-info.yaml
• changed github issue template file

[openedx-webhooks]

Thanks for the pull request, @ichintanjoshi! Please note that it may take us up to several weeks or months to complete a review and merge your PR.

Feel free to add as much of the following information to the ticket as you can:

• supporting documentation
• Open edX discussion forum threads
• timeline information ("this must be merged by XX date", and why that is)
• partner information ("this is a course on edx.org")
• any other information that can help Product understand the context for the PR

All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here.

Please let us know once your PR is ready for our review and all tests are green.

[sarina]

@ichintanjoshi - looks like there's some yaml linting errors on the catalog-info. You should check those, and make sure any errors are corrected on other PRs.

[ichintanjoshi]

@ichintanjoshi - looks like there's some yaml linting errors on the catalog-info. You should check those, and make sure any errors are corrected on other PRs.

Yes @sarina on it

[ichintanjoshi]

Updated linting @sarina

[sarina]

hey @ichintanjoshi I am waiting in #621 as well as in #dev in slack to get an answer on whether or not we can decrease the codecov threshold (or scrap codecov altogether), I'll merge this when I have a solution.

[sarina]

@ichintanjoshi - I can't seem to edit your branch. Could you do the following, then I will merge?

• Rebase the branch on master
• Squash to two commits (chore: add catalog-info.yml and chore: enable github issues via config file)

[mphilbrick211]

@sarina @ichintanjoshi - just following up on this.

[ichintanjoshi]

@sarina @ichintanjoshi - just following up on this.

@sarina Have rebased

[sarina]

@ichintanjoshi can you address this feedback from my last comment?

Squash to two commits (chore: add catalog-info.yml and chore: enable github issues via config file)

This will require an interactive rebase, not merging master into this branch.

[sarina]

You will need to run

git rebase -i HEAD~8

to get at the comments in your branch, and then use the commands in interactive rebase to move and squash commits. We follow a rebasing workflow so it is wise to get used to actually rebasing rather than merging in master. I can only squash your commits down to one commit via the GitHub UI, and I want to maintain the two different changes made in this branch. https://hackernoon.com/beginners-guide-to-interactive-rebasing-346a3f9c3a6d

Alternatively, you can close this PR and make a new one with the changes properly separated out, although I think that's more work.

[openedx-webhooks]

@ichintanjoshi Even though your pull request wasn’t merged, please take a moment to answer a two question survey so we can improve your experience in the future.

[ichintanjoshi]

@sarina closing this as I think I messed up the rebasing part, will raise a new one