nbdev_new fails on hosted GitHub Enterprise due to outdated workflow repository path

[n-e-w]

Description

When using nbdev_new on GitHub Enterprise accounts, the initial workflow fails because it's trying to use fastai/workflows which now redirects to answerdotai/workflows. While regular GitHub accounts follow this redirect automatically, Enterprise accounts are more strict about redirects, causing the workflow to fail.

Current Behavior

• nbdev_new creates workflows referencing fastai/workflows
• On GitHub Enterprise, this fails with error: Error: Unable to resolve action. Repository not found: fastai/workflows
• Works on regular GitHub accounts due to automatic redirect handling

Expected Behavior

• nbdev_new should use answerdotai/workflows directly
• This would work on both regular and Enterprise GitHub accounts

Files Affected

• The template files that nbdev_new uses to generate:
  • .github/workflows/test.yaml
  • .github/workflows/deploy.yaml

Additional Context

This particularly affects Enterprise users but updating the paths would be beneficial for all users as it would remove dependency on the redirect.

Minimal Reproducible Example

Setup to Reproduce

1. Create new repo on GitHub Enterprise
2. Clone locally
3. Setup Python environment and install requirements:

   uv pip install jupyterlab nbdev

4. Initialize nbdev project:

   nbdev_new

5. Push to GitHub:

   git add .
   git commit -m "Initial commit"
   git push

Error

In GitHub Actions, the initial workflow fails with:

Error: Unable to resolve action. Repository not found: fastai/workflows

Fix

Modifying .github/workflows/test.yaml and .github/workflows/deploy.yaml to use answerdotai/workflows instead of fastai/workflows resolves the issue.

Technical Details

• This specifically affects GitHub Enterprise accounts
• Regular GitHub accounts work because they automatically handle the repository redirect from fastai/workflows to answerdotai/workflows
• Enterprise GitHub has stricter security settings that prevent following this redirect

Error Example

https://github.com/IQX-AI/nbdev_enterprise_test/actions/runs/13281269255/job/37079966531

[n-e-w]

I'm working on a fix for this which i'm going to test in conjunction with nbdev-template and from within nbdev itself. Should submit some PRs over the next 12 hours or so.