Issue template for notebook updates

[ateucher]

An issue template for proposing notebook updates based on #425 by @mikala-nsidc. A companion to the "remove notebook" template merged in #423

[Copilot]

Pull request overview

Adds a new GitHub Issue Form template to propose updates to cookbook notebook/page content (companion to the previously added “remove notebook” template).

Changes:

• Introduces an “Update notebook” issue template with fields for target content, what’s out of date/missing, recommended updates, and context.
• Adds a “Decision” checkbox section to record the outcome before opening a PR or closing the issue.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[github-actions]

🚀 Deployed on https://deploy-preview-428--openscapes-org-preview.netlify.app

[itcarroll]

What do you think about changing the "Decision" section to something more informational? I'm doubtful the checkboxes will be successfully used. Checkboxes also aren't an "either-or" data field, possibly leading to some confusion with "to-do" checkboxes. How about this markdown type section as an alternative:

For the update template:

  - type: markdown
    attributes:
      value: |
        ## Final resolution
        After discussion, how this feedback is addressed will show up in how the issue is resolved.
        1. Closed as completed: Merging a PR to update this notebook automatically closes this issue.
        2. Closed as won't fix: The author or maintainer closes this issue manually if no changes are necessary.
        3. Closed as duplicate: The author or maintainer closes this issue after linking a similar issue.

For the remove template:

  - type: markdown
    attributes:
      value: |
        ## Final resolution
        After discussion, how this feedback is addressed will show up in how the issue is resolved.
        1. Closed as completed: Merging a PR to remove this notebook automatically closes this issue.
        2. Closed as won't fix: The author or maintainer closes this issue manually if no changes are necessary.
        3. Closed as duplicate: The author or maintainer closes this issue after linking a new issue from the "Update notebook" template.

Not sure about exact wording yet, so I didn't want to put this in as a code suggestion.

[ateucher]

I like that idea @itcarroll, it's a bit clearer. Do you think we should link to the other issue templates (i.e., if someone opens an issue to remove a notebook, but it becomes clear that just an update would be better they should open an "update" issue?

[itcarroll]

I've gone ahead with some additional enhancements beyond the scope of the original issue for consistency.

I think we won't be able to see if this is all "working" until its merged to main. I'm available to rapidly take up fixes as needed.

[ateucher]

Thanks @itcarroll great changes! I had a two small comments, otherwise I think you can merge this. I can't approve since I'm the original PR author