Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Sign up
Appearance settings

Moving LambdaTest to Development Partner #2265

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

Merged
diemol merged 1 commit into trunk from lambdatest-partner
Apr 8, 2025
Merged

Conversation

@diemol
Copy link
Member

@diemol diemol commented Apr 8, 2025 •
edited by qodo-merge-pro bot
Loading

User description

Thanks for contributing to the Selenium site and documentation!
A PR well described will help maintainers to review and merge it quickly

Before submitting your PR, please check our contributing guidelines.
Avoid large PRs, and help reviewers by making them as simple and short as possible.

Description

After a strong commitment from LambdaTest, now they move to Development Partners 🎉

Motivation and Context

Types of changes

  • Change to the site (I have double-checked the Netlify deployment, and my changes look good)
  • Code example added (and I also added the example to all translated languages)
  • Improved translation
  • Added new translation (and I also added a notice to each document missing translation)

Checklist

  • I have read the contributing document.
  • I have used hugo to render the site/docs locally and I am sure it works.

PR Type

Enhancement, Documentation

Description

  • Added LambdaTest as a Development Partner in sponsorship data.

  • Updated sponsorship level details to reflect new partner limits.

  • Minor formatting adjustments in the sponsorship benefits section.

Changes walkthrough 📝

Relevant files
Documentation
_index.html
Update sponsorship benefits and formatting

website_and_docs/content/sponsor/_index.html

  • Adjusted text formatting in the sponsorship benefits section.
  • Updated the limit of companies for a sponsorship level from 2 to 3.
  • Removed unnecessary paragraph tags for cleaner HTML structure.
    • +3/-3
    Enhancement
    sponsors.yml
    Add LambdaTest as Development Partner in sponsors data

    website_and_docs/data/sponsors.yml

  • Added LambdaTest under the "Development" sponsorship level.
  • Removed LambdaTest from the "Selenium" sponsorship level.
  • Updated sponsorship renewal details for LambdaTest.
    • +4/-4
    Need help?
  • Type /help how to ... in the comments thread for any questions about Qodo Merge usage.
  • Check out the documentation for more information.
    •

    harsha509 and saikrishna321 reacted with hooray emoji
    Copy link
    Contributor

    qodo-merge-pro bot commented Apr 8, 2025

    PR Reviewer Guide 🔍

    Here are some key observations to aid the review process:

    ⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪
    🧪 No relevant tests
    🔒 No security concerns identified
    ⚡ No major issues detected

    Copy link
    Contributor

    qodo-merge-pro bot commented Apr 8, 2025

    PR Code Suggestions ✨

    Explore these optional code suggestions:

    CategorySuggestion Impact
    Possible issue
    Fix incorrect future date

    The renewal date "April 8, 2025" is set to the future (today's date is specified
    as 2025年04月08日). This appears to be a critical date error that could cause
    confusion about when the sponsorship was actually renewed.

    website_and_docs/data/sponsors.yml [12] 

    -+ # Sponsorship renewed October 16, 2024. Renewed again on April 8, 2025, under the "Development" level
++ # Sponsorship renewed October 16, 2024. Moved to "Development" level on April 8, 2025

    [To ensure code accuracy, apply this suggestion manually]

    Suggestion importance[1-10]: 9

    __

    Why: The suggestion correctly identifies a critical date error in the comment. Having a future renewal date (April 8, 2025) would be misleading and confusing to users and sponsors. The improved wording clarifies the timeline of events more accurately.

    		High
    • More

    Copy link

    netlify bot commented Apr 8, 2025

    ✅ Deploy Preview for selenium-dev ready!

    Name Link
    🔨 Latest commit 39e99c1
    🔍 Latest deploy log https://app.netlify.com/sites/selenium-dev/deploys/67f539cac3bc0a0008c23309
    😎 Deploy Preview https://deploy-preview-2265--selenium-dev.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.

    @diemol diemol merged commit a6d9dbf into trunk Apr 8, 2025
    6 checks passed
    @diemol diemol deleted the lambdatest-partner branch April 8, 2025 18:28
    selenium-ci added a commit that referenced this pull request Apr 8, 2025
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

    Reviewers

    @maaretp maaretp maaretp approved these changes

    Assignees

    No one assigned

    Projects

    None yet

    Milestone

    No milestone

    Development

    Successfully merging this pull request may close these issues.

    AltStyle によって変換されたページ (->オリジナル) /