Add a workflow for generating Hackday Github Discussion threads

[Sherwin-14]

I have replaced the CATEGORY_ID and REPOSITORY_ID, though, it remains untested. (It would be funny if Github allowed me to open a discussions thread in another repository 😆)

---

📚 Documentation preview 📚: https://earthaccess--914.org.readthedocs.build/en/914/

[github-actions]

👈 Launch a binder notebook on this branch for commit aab593c

I will automatically update this comment whenever this PR is modified

👈 Launch a binder notebook on this branch for commit f0baaa6

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

[mfisher87]

Since this isn't a user-facing change to earthaccess, I think we should omit this from the changelog!

[mfisher87]

@asteiker @betolink @ateucher I don't think I'll be available for tomorrow's hack day; are one of you willing to give this a shot?

Click the Actions tab, then select "Generate Discussion Thread for Hackdays", then click "Run workflow" to use.

[mfisher87]

Looks great, thank you @Sherwin-14 :)

[mfisher87]

@Sherwin-14 tried to do a test run and got:

gh: Could not resolve to a node with the global id of 'DIC_kwDOF9V-ic4CdYaN!'
{"data":{"createDiscussion":null},"errors":[{"type":"NOT_FOUND","path":["createDiscussion"],"locations":[{"line":3,"column":3}],"message":"Could not resolve to a node with the global id of 'DIC_kwDOF9V-ic4CdYaN!'"}]}

https://github.com/nsidc/earthaccess/actions/runs/12636855658/job/35209870757

Any ideas?

[mfisher87]

Looks like the category ID doesn't exactly match. I was able to successfully query from my local machine with:

  gh api graphql -f query='
  mutation
   {createDiscussion
     (
       input:
         {
         repositoryId: "MDEwOlJlcG9zaXRvcnkzOTk4Njc1Mjk=",
         categoryId: "DIC_kwDOF9V-ic4CdYaN",
         body: "Reporting out on earthaccess hack days. Use the comment button at the very bottom to send a message. Additionally, consider sending issues and PRs relevant to your work to help make the job of future readers easier. It is okay to duplicate information here! Use the reply feature to have a discussion under any comment. Enjoy!",
         title: "Hackathon 2025/01/06"
         }
     )
     {
       discussion {id}
     }
   }'

Note the trailing ! on categoryId is removed. I also needed to mess with the quotes a little.

[Sherwin-14]

How about we rely on secrets. this may be more flexible, what do you think?

…

On Mon, 6 Jan, 2025, 10:44 pm Matt Fisher, ***@***.***> wrote: Looks like the category ID doesn't exactly match. I was able to successfully query from my local machine with: gh api graphql -f query=' mutation {createDiscussion ( input: { repositoryId: "MDEwOlJlcG9zaXRvcnkzOTk4Njc1Mjk=", categoryId: "DIC_kwDOF9V-ic4CdYaN", body: "Reporting out on earthaccess hack days. Use the comment button at the very bottom to send a message. Additionally, consider sending issues and PRs relevant to your work to help make the job of future readers easier. It is okay to duplicate information here! Use the reply feature to have a discussion under any comment. Enjoy!", title: "Hackathon 2025/01/06" } ) { discussion {id} } }' Note the trailing ! on categoryId is removed. I also needed to mess with the quotes a little. — Reply to this email directly, view it on GitHub <#914 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BBV63P3MRC4VSJHKLS6FE3L2JK2YPAVCNFSM6AAAAABUULGINWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZTGU2TAMJQGA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[mfisher87]

Since these values are publicly accessible, I think it's fine to keep them as in-line envvars in the action :) Did you have another reason I'm missing?

Fixed with #917 !

[ateucher]

@mfisher87 @Sherwin-14 This is great, I'll give it a shot tomorrow!

[mfisher87]

🙌 Thanks Andy!

[mfisher87]

@ateucher I granted you write access to this repository; it's required to run workflows. Please accept the invitation here: https://github.com/nsidc/earthaccess/invitations

[ateucher]

Accepted, thanks @mfisher87 !