-
-
Notifications
You must be signed in to change notification settings - Fork 2
Add runTests command for v2 test runs #47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
- Removed the 'command' input from both main.yml and test-current-release.yml workflows. - Updated version input in action.yml to be optional and modified its description. - Adjusted index.js to handle version input more flexibly, defaulting to the installed version if not specified.
- Create a new workflow file to run Doc Detective locally - Define inputs for runner, working directory, configuration, and more - Set permissions for contents, issues, and pull requests - Configure job to run on ubuntu-latest and execute the action
- Add postbuild script to run tests after build - Change test command to run with local job - Update license from MIT to AGPL-3.0-only
- Create a new YAML file for test specifications - Define a simple test step to run a shell command
- Simplify configuration by removing unused properties - Set input to specific test specification file - Maintain log level and telemetry settings
- Change 'startRecording' to 'record' in the warning message - Clarify that tests requiring the 'record' step need macOS or Windows runners
- Change input file from tests.spec.json to tests.spec.yaml - Set log level to debug
- Change 'required' field for 'version' input from true to false
- Change input path for pass-tests to use relative path - Change input path for fail-tests to use relative path
- Replace comment syntax with HTML comments for test sections - Update links to use HTTPS - Clean up unnecessary comment lines
- Bump package version to 1.3.1. - Update @actions/github dependency to version 6.0.1.
|
Warning Rate limit exceeded@hawkeyexl has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 18 minutes and 23 seconds before requesting another review. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ⛔ Files ignored due to path filters (2)
📒 Files selected for processing (4)
✨ Finishing Touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
No description provided.