Move this project to Bad Idea Factory

[slifty]

I started this locally to experiment, but now that it's something I think is worth publishing I'd like to publish it via BIF instead of personally.

[slifty]

I believe CI is failing because BIF doesn't have a copilot license, which is fine!

To that end I may update the workflow somehow.

[github-actions]

QA Instructions

Summary

This PR updates the project to reflect its transfer from a personal repository to the Bad Idea Factory organization. It primarily updates URLs and package references from slifty to BadIdeaFactory. Additionally, new instructions for enabling GitHub Models at the organizational level are included in the README. Minor updates are also made to package-lock.json to remove unnecessary properties.

---

Test Scenarios

1. Validate Repository URL Changes

   • Steps:
     1. Navigate to the repository's new GitHub page: https://github.com/BadIdeaFactory/qa-instructions-action.
     2. Confirm that the repository is accessible and matches the expected contents of the previous slifty repository.
   • Expected Result: Repository is publicly accessible, and content matches the previous repository.

2. Verify README Updates

   • Steps:
     1. Open the updated README.md file.
     2. Check that all references to the repository URL now point to https://github.com/BadIdeaFactory/qa-instructions-action.
     3. Review the updated troubleshooting steps for enabling GitHub Models in the "Troubleshooting" section.
   • Expected Result:
     • All references use the new organization URL.
     • Instructions for enabling GitHub Models are clear, accurate, and complete.

3. Test GitHub Action with Updated URLs

   • Steps:
     1. Integrate the updated action (- uses: BadIdeaFactory/qa-instructions-action@v1) into a test repository's workflow file.
     2. Push a PR to the test repository.
     3. Confirm that the action executes successfully and comments testing instructions on the PR.
   • Expected Result: The action runs without errors, and the comment includes proper QA instructions.

4. Validate Alternative Provider Instructions

   • Steps:
     1. Set up a workflow in a test repository using the provider: anthropic option and the updated action path.
     2. Ensure the repo contains a valid ANTHROPIC_API_KEY secret.
     3. Push a PR to the test repository and verify the action behavior.
   • Expected Result: Action successfully interacts with the Anthropic API and posts QA instructions.

5. Verify Backward Compatibility

   • Steps:
     1. Test an old workflow referencing slifty/qa-instructions-action@v1.
     2. Push a PR to verify if the action is still supported via the old repository path.
   • Expected Result: The action either redirects seamlessly or fails gracefully with a clear error about the incorrect repository path.

6. Check for Errors in Package Updates

   • Steps:
     1. Run npm install to install dependencies.
     2. Run npm run build to ensure the build process works.
     3. Execute the project's test suite with npm test.
   • Expected Result: No dependency errors during installation. Build succeeds, and all tests pass.

---

Regression Risks

1. GitHub Action Integration: Since repository links and configurations are updated, existing workflows referencing the old slifty repository may stop functioning. Ensure backward compatibility is documented or addressed.
2. Package Lock Changes: Changes to package-lock.json may indirectly introduce dependency issues. Verify that all dependencies are correctly resolved and functional.

---

Things to Watch For

1. Ensure GitHub Actions using the updated repository URL (BadIdeaFactory) are correctly implemented and do not produce errors when executed.
2. Confirm that the documentation (e.g., updated troubleshooting steps) aligns with the actual observed behavior of enabling GitHub Models at the organizational level.

---

Generated by QA Instructions Action