Skip to content

Add GitHub Action to check for FIMS releases and create update issues#3

Closed
Copilot wants to merge 13 commits intomainfrom
copilot/add-github-action-for-updates
Closed

Add GitHub Action to check for FIMS releases and create update issues#3
Copilot wants to merge 13 commits intomainfrom
copilot/add-github-action-for-updates

Conversation

Copy link
Copy Markdown

Copilot AI commented Nov 25, 2025

Adds a scheduled workflow to monitor FIMS releases and automatically create tracking issues when updates are needed.

Changes

  • New workflow: .github/workflows/check-fims-release.yml
    • Runs every Monday and Wednesday at 9:00 AM UTC
    • Queries latest release from noaa-fims/fims
    • Creates issue with title "Update repository for FIMS {tag}"
    • Assigns to @Andrea-Havron-NOAA
    • Sets issue type to "Task" via GraphQL API
    • Applies labels: auto-update, kind: refactor
    • Skips if issue for that release already exists
    • Graceful error handling for missing labels/assignee

Notes

Uses GraphQL for issue creation to support GitHub's issue types feature (not available via REST API). Manual trigger via workflow_dispatch available for testing.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

  • https://api.github.com//advisories
    • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node /home/REDACTED/work/_temp/ghcca-node/node/bin/node --enable-source-maps /home/REDACTED/work/_temp/copilot-developer-action-main/dist/index.js (http block)
  • https://api.github.com/repos/NOAA-FIMS/FIMSRTMB/issues/2
    • Triggering command: /usr/bin/curl curl -s REDACTED (http block)

If you need me to access, download, or install something from one of these locations, you can either:

Original prompt

This section details on the original issue you should resolve

<issue_title>[Developer Issue]: Update upon release</issue_title>
<issue_description>### Description

This repository needs a GitHub action to remind us to update it upon every release of FIMS. I think that the action should look for releases in noaa-fims/fims on a schedule, i.e., every Monday and Wednesday morning. If a new release is found, then an Issue should be opened in this repository mentioning the release number of FIMS and stating that this repository should be updated. The issue should be assigned to @Andrea-Havron-NOAA with an "Issue type" of "Task" and labels of "auto-update" "kind: refactor".</issue_description>

Comments on the Issue (you are @copilot in this section)


💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

Bai-Li-NOAA and others added 11 commits July 29, 2025 13:55
* set verbosity to `quiet` in `tests/testthat.R` to suppress test output
  when running `devtools::test()` locally.
* set verbosity to `quiet` in `tests/testthat/helper-aaa-quiet-test-output.R`
  to suppress output when running `testthat::test_package()` locally.
  This mirrors the "Show testthat output" (`test_check()`) step in the
  `call-r-cmd-check` GitHub Action workflow.
* set `silent = TRUE` in `TMB::MakeADFun()` calls to
  suppress TMB output during tests.
* use `suppressMessages()` to silence output from fims_frame tests and
  testthat template tests.
* don't use `Rcerr` to print a message to the console when the ParameterVector
  index is out of range, since `throw` already handles the error output.
Bumps [actions/first-interaction](https://github.com/actions/first-interaction) from 1 to 2.
- [Release notes](https://github.com/actions/first-interaction/releases)
- [Commits](actions/first-interaction@v1...v2)

---
updated-dependencies:
- dependency-name: actions/first-interaction
  dependency-version: '2'
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
* document(check_fims.R): Add examples of strings passed to ... in
  FIMS:::setup_and_run_gtest()
* refactor(fimsfit.R):
  * Remove is.FIMSFits() function
  * Remove "total" from number_of_parameters; only print it
    as the sum of fixed_effects + random_effects
* document(fimsfit.R): Add comment referencing sdmTMB issue NOAA-FIMS#455 to
  evaluate whether report should always use last.par.best
* document(initialize_modules.R): Clarify that dims field is necessary
  to track dimensions for multivariate input (e.g., MVNORM) and may be
  needed for other distributions
* update(data1.R): Remove check for CSV readability in R
* update(helper-integration-tests-setup-function.R): Replace 1:x with
  seq_along() in for loop for safer indexing

Co-authored-by: Andrea-Havron-NOAA <Andrea-Havron-NOAA@users.noreply.github.com>
Co-authored-by: k-doering-NOAA <k-doering-NOAA@users.noreply.github.com>
Co-authored-by: kellijohnson-NOAA <kellijohnson-NOAA@users.noreply.github.com>
Co-authored-by: msupernaw <msupernaw@users.noreply.github.com>
Co-authored-by: nathanvaughan-NOAA <nathanvaughan-NOAA@users.noreply.github.com>
Co-authored-by: peterkuriyama-NOAA <peterkuriyama-NOAA@users.noreply.github.com>
* add README.md under the /tests directory as a quick reference for
  testing. It includes instructions on adding a new test, run tests, and
  debug tests.
* add a C++ test template to inst/templates.
* add a new R function `use_gtest_template()` to create a C++ test file
  using the template and register the test in
  `tests/gtest/CMakeLists.txt`.
* add R unit tests for `use_gtest_template()`.
* add a C++ test `tests/gtest/test_FIMSJson_JsonParser_WriteToFile.cpp`
  to verify error handling instructions outlined in the C++ test template.
* update LogisticSelectivity C++ test to use the new template.
* fix spelling errors and update WORDLIST.
* Place `Rcpp::loadModule(module = "fims", what = TRUE)` inside the
  `.onLoad` function has been observed to fix R session crashes when running
  `devtools::load_all()` followed by `devtools::test()` in the package
  development workflow.
Copilot AI and others added 2 commits November 25, 2025 16:11
Co-authored-by: kellijohnson-NOAA <4108564+kellijohnson-NOAA@users.noreply.github.com>
…flow

Co-authored-by: kellijohnson-NOAA <4108564+kellijohnson-NOAA@users.noreply.github.com>
Copilot AI changed the title [WIP] Add GitHub action to remind updates on releases Add GitHub Action to check for FIMS releases and create update issues Nov 25, 2025
@kellijohnson-NOAA
Copy link
Copy Markdown

@Andrea-Havron-NOAA I am going to assign you to this PR because I am uncertain if it should be merged into dev right now or a different branch. If we get it merged in by the end of the week to main then we can check to see if it works with the next FIMS release.

@kellijohnson-NOAA kellijohnson-NOAA requested review from Andrea-Havron-NOAA and removed request for kellijohnson-NOAA November 25, 2025 16:33
@kellijohnson-NOAA kellijohnson-NOAA removed their assignment Nov 25, 2025
@Andrea-Havron-NOAA Andrea-Havron-NOAA marked this pull request as ready for review April 7, 2026 18:28
@Andrea-Havron-NOAA Andrea-Havron-NOAA changed the base branch from dev to main April 7, 2026 18:29
@Andrea-Havron-NOAA
Copy link
Copy Markdown

replaced with PR #6

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Developer Issue]: Update upon release

5 participants