Skip to content
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

fix: restrict markdown tests to ubuntu runner #3317

Closed
wants to merge 3 commits into from

Conversation

anshgoyalevil
Copy link
Member

@anshgoyalevil anshgoyalevil commented Oct 23, 2024

This PR restricts markdown tests to Ubuntu Runner since we cannot make use of commands like sed in Windows bash.

Summary by CodeRabbit

  • Chores
    • Updated workflow conditions to restrict markdown checks and comments to the 'ubuntu-latest' operating system, improving execution efficiency.
    • Changed the event trigger for pull request testing to enhance permissions and access to pull request content.

Copy link

coderabbitai bot commented Oct 23, 2024

Walkthrough

The pull request modifies the Node.js workflow file for pull request testing by changing the event trigger from pull_request to pull_request_target. It adds conditional logic to restrict certain steps, such as markdown checks and related actions, to execute only on the 'ubuntu-latest' operating system. The overall workflow structure remains intact, but the execution context for specific tasks is now limited, enhancing control flow and error handling for markdown checks.

Changes

File Path Change Summary
.github/workflows/if-nodejs-pr-testing.yml Changed event trigger to pull_request_target and added conditions for markdown checks to run only on 'ubuntu-latest'.

Possibly related PRs

  • fix: run tests on branch pushes #3296: This PR modifies the same workflow file (if-nodejs-pr-testing.yml), focusing on testing triggers and conditions, which may relate to the overall workflow structure and execution logic.
  • test: add markdown tests #3301: This PR also updates the same workflow file (if-nodejs-pr-testing.yml) by adding markdown checks, which aligns with the main PR's focus on refining conditional checks and execution based on specific criteria.

Suggested labels

ready-to-merge

Suggested reviewers

  • derberg
  • magicmatatjahu
  • devilkiller-ag
  • sambhavgupta0705
  • asyncapi-bot-eve
  • Mayaleeeee
  • akshatnema

🐇 In the meadow where bunnies play,
Markdown checks come out to stay.
On 'ubuntu-latest', they hop with glee,
Ensuring our code is as clean as can be!
With conditions set, they dance and prance,
In the world of code, they take their chance! 🌼


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 54aa39d and e6e4607.

📒 Files selected for processing (1)
  • .github/workflows/if-nodejs-pr-testing.yml (4 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • .github/workflows/if-nodejs-pr-testing.yml

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

netlify bot commented Oct 23, 2024

Deploy Preview for asyncapi-website ready!

Built without sensitive environment variables

Name Link
🔨 Latest commit 0bc05af
🔍 Latest deploy log https://app.netlify.com/sites/asyncapi-website/deploys/6718c2aaf43a3000085f63ba
😎 Deploy Preview https://deploy-preview-3317--asyncapi-website.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@@ -76,7 +76,7 @@ jobs:
run: npm run generate:assets --if-present

# Run the test:md script and capture output
- if: steps.packagejson.outputs.exists == 'true'
- if: ${{ steps.packagejson.outputs.exists == 'true' && matrix.os == 'ubuntu-latest' }}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are we restricting the tests to ubuntu os only?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Because we are using the commands like sed to parse the errors, windows bash doesn't have that support

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (1)
.github/workflows/if-nodejs-pr-testing.yml (1)

Line range hint 79-87: Consider adding error handling for the test:md script.

While the implementation works, it might silently fail if the test:md script exits with an error.

Consider adding error handling:

 - if: ${{ steps.packagejson.outputs.exists == 'true' && matrix.os == 'ubuntu-latest' }}
   name: Run markdown checks
   id: markdown_check
   run: |
+    set -eo pipefail
     ERRORS=$(npm run test:md | sed -n '/Errors in file/,$p')
     echo "markdown_output<<EOF" >> $GITHUB_OUTPUT
     echo "$ERRORS" >> $GITHUB_OUTPUT
     echo "EOF" >> $GITHUB_OUTPUT
🧰 Tools
🪛 actionlint

82-82: shellcheck reported issue in this script: SC2129:style:2:1: Consider using { cmd1; cmd2; } >> file instead of individual redirects

(shellcheck)


82-82: shellcheck reported issue in this script: SC2086:info:2:32: Double quote to prevent globbing and word splitting

(shellcheck)


82-82: shellcheck reported issue in this script: SC2086:info:3:19: Double quote to prevent globbing and word splitting

(shellcheck)


82-82: shellcheck reported issue in this script: SC2086:info:4:15: Double quote to prevent globbing and word splitting

(shellcheck)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 0b09994 and 54aa39d.

📒 Files selected for processing (1)
  • .github/workflows/if-nodejs-pr-testing.yml (3 hunks)
🧰 Additional context used
🔇 Additional comments (2)
.github/workflows/if-nodejs-pr-testing.yml (2)

Line range hint 79-87: LGTM! Markdown checks are now properly restricted to Ubuntu.

The implementation correctly restricts the markdown checks to Ubuntu, addressing the sed command compatibility issue. The error capture and output handling are well implemented.

🧰 Tools
🪛 actionlint

82-82: shellcheck reported issue in this script: SC2129:style:2:1: Consider using { cmd1; cmd2; } >> file instead of individual redirects

(shellcheck)


82-82: shellcheck reported issue in this script: SC2086:info:2:32: Double quote to prevent globbing and word splitting

(shellcheck)


82-82: shellcheck reported issue in this script: SC2086:info:3:19: Double quote to prevent globbing and word splitting

(shellcheck)


82-82: shellcheck reported issue in this script: SC2086:info:4:15: Double quote to prevent globbing and word splitting

(shellcheck)


Line range hint 90-110: LGTM! PR comment handling is properly implemented.

The implementation correctly handles both the creation and deletion of PR comments based on markdown check results, and is properly restricted to Ubuntu runner.

@asyncapi-bot
Copy link
Contributor

asyncapi-bot commented Oct 23, 2024

⚡️ Lighthouse report for the changes in this PR:

Category Score
🔴 Performance 46
🟢 Accessibility 98
🟢 Best practices 92
🟢 SEO 100
🔴 PWA 33

Lighthouse ran on https://deploy-preview-3317--asyncapi-website.netlify.app/

@anshgoyalevil anshgoyalevil reopened this Oct 23, 2024
@anshgoyalevil anshgoyalevil reopened this Oct 23, 2024
@anshgoyalevil anshgoyalevil deleted the check_md_test branch October 23, 2024 12:15
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.

3 participants