Trigger FUSE runtest

[jguterl]

@orso82 @bclyons12 I'm trying to trigger the runtests workflow for FUSE from this package to ensure that development of ADAS.jl from other projects do not break FUSE.
Can you add a secret "PAT_FUSE" to the FUSE repo for that purpose?
Workflow is here: https://github.com/ProjectTorreyPines/ADAS.jl/blob/master/.github/workflows/runtest_FUSE.yml

[orso82]

@jguterl the way we test change with FUSE is that we open a PR on the FUSE side on a branch with the same name of what you are using in ADAS.jl. This allows us to test sets of changes that occur on different repositories.

If you really want you do it your way, you can simply use the PTP_READ_TOKEN secret which is setup at the organization level, and gives access to the project-torrey-pines user that has read permission to the ADAS.jl repo (as well as all the other FUSE-related repos).

[orso82]

@jguterl as we move towards versioning our packages, I don't think you should worry about running FUSE tests.
FUSE will point to whatever version of ADAS.jl that works with it. If there's a new version of ADAS.jl, the FUSE CompatHelper will run the tests and flag if there's any problem.

It's actually more important that the ADAS.jl tests run. Can you check what's breaking them?