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

point shielding in README #2116

Merged
merged 1 commit into from Jan 25, 2024
Merged

point shielding in README #2116

merged 1 commit into from Jan 25, 2024

Conversation

Doofus100500
Copy link
Contributor

Thanks for contributing to the Docker-Selenium project!
A PR well described will help maintainers to quickly review and merge it

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

Description

Motivation and Context

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist

  • I have read the contributing document.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

@VietND96 VietND96 merged commit b9c8494 into SeleniumHQ:trunk Jan 25, 2024
1 check passed
@VietND96
Copy link
Member

@Doofus100500, thank you for your looking into chart README!

@Doofus100500 Doofus100500 deleted the patch-1 branch January 25, 2024 10:02
@VietND96
Copy link
Member

@Doofus100500, btw, did you try the RCLONE configs in the chart? Is it easy and flexible?

@Doofus100500
Copy link
Contributor Author

@VietND96 Yes, everything is great! I'm passing the config using --set-file by substituting a GitLab variable of file type.

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.

None yet

2 participants