Update issue templates

[JessicaS11]

No description provided.

[github-actions]

👈 Launch a binder notebook on this branch for commit 9de6ac2

I will automatically update this comment whenever this PR is modified

👈 Launch a binder notebook on this branch for commit bdd0219

👈 Launch a binder notebook on this branch for commit 57c71a5

👈 Launch a binder notebook on this branch for commit a0d0c12

👈 Launch a binder notebook on this branch for commit 0dfeea6

👈 Launch a binder notebook on this branch for commit 739eac3

👈 Launch a binder notebook on this branch for commit dcea109

👈 Launch a binder notebook on this branch for commit 989642a

👈 Launch a binder notebook on this branch for commit f945fd9

👈 Launch a binder notebook on this branch for commit d95058b

👈 Launch a binder notebook on this branch for commit cd8d176

👈 Launch a binder notebook on this branch for commit 53e29f6

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 65.83%. Comparing base (7251f19) to head (53e29f6).
⚠️ Report is 11 commits behind head on development.

Additional details and impacted files

@@             Coverage Diff              @@
##           development     #728   +/-   ##
============================================
  Coverage        65.83%   65.83%           
============================================
  Files               37       37           
  Lines             3050     3050           
  Branches           394      394           
============================================
  Hits              2008     2008           
  Misses             971      971           
  Partials            71       71           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[rwegener2]

I just updated these to be more tailored to icepyx! Changes:

• feature request template: I didn’t change much other than inserting “icepyx” where the template said “our project”
• bug report template: I switched to yaml because I wanted to add a bit of new functionality (Ex. having a place where a user could include a code block; specify placeholder text; …)

Ready for review. I just requested @asteiker (@JessicaS11 I can’t request you, I assume because you opened the initial PR).

@JessicaS11 do you have any insight on the failing integration check? The error is User **pre-commit-ci[bot]** does not have permission to run integration tests and it looks like it’s a required check.

[JessicaS11]

do you have any insight on the failing integration check? The error is User pre-commit-ci[bot] does not have permission to run integration tests and it looks like it’s a required check.

That one is when precommit runs and thus the last commit is from the bot, it doesn't have access to the secrets required for the integration tests. I'm not sure if there's an easy way to fix that. Either way, the integration tests will still fail because I just updated them for v007 file IDs and sizes (#727), but for some reason v006 granules are being returned now (versus last week when I first updated them). I'm working with NSIDC on it.

[asteiker]

@rwegener2 These are great additions! I don't have any suggestions in terms of the content, though I pasted in the errors that I received when I viewed the file within GitHub. I don't have time atm to suggest updates other than posting those messages, but happy to look into this after AGU (though I admit I don't have any experience with these).

[asteiker]

When I went to view the file, several problems were listed at the top. Copying them into each relevant section:

title must be of type String and cannot be empty. Learn more about error 1.

[asteiker]

Listed when I went to View File:

assignees must be of type String or Array. Learn more about error 2.

[asteiker]

labels must be of type String or Array. Learn more about error 3.

[asteiker]

projects must be of type String or Array. Learn more about error 4.

[rwegener2]

… though I pasted in the errors that I received when I viewed the file within GitHub

Thanks so much @asteiker, this is really helpful!

Where did you go to see those error messages? I don’t think I’m seeing them when I just open the file in the “Files Changed” section of the PR Nevermind, I found it by viewing the file in the issue-templates branch. Thanks for pointing that out, I didn’t realize you could do that! I’ll go through and fix those syntax errors.

[JessicaS11]

Should we make the input format consistent (i.e. make these input boxes as well, where presumably the instructions are temporary text or separate from the response without the user manually deleting)?

[JessicaS11]

This looks great, @rwegener2! Thank you! I added a few minor formatting notes, but happy for you to approve and merge this PR whenever.

[rwegener2]

Thanks for the review @JessicaS11! I updated the templated addressing your comments.

I actually am not allowed to squash and merge, I think because the Integration Test is marked a a required test. Is there a work-around for that?

[asteiker]

@rwegener2 Sorry for missing your question on viewing the files and associated warnings! Glad you found it. Yes I was also able to do this from the PR by clicking on Files Changed tab and clicking the three dots at the top of the file -> View file.

[JessicaS11]

I actually am not allowed to squash and merge, I think because the Integration Test is marked a a required test. Is there a work-around for that?

I use my admin privileges to check the box allowing us to bypass the rules... not my favorite to use, but until we get them debugged/fixed...