Contributing to the Selenium site & documentation
Selenium is a big software project, its site and documentation are key to understanding how things work and learning effective ways to exploit its potential.
This project contains both Selenium’s site and documentation. This is an ongoing effort (not targeted at any specific release) to provide updated information on how to use Selenium effectively, how to get involved and how to contribute to Selenium.
Contributions toward the site and docs follow the process described in the below section about contributions.
The Selenium project welcomes contributions from everyone. There are a number of ways you can help:
Report an issue
When reporting a new issues or commenting on existing issues please make sure discussions are related to concrete technical issues with the Selenium software, its site and/or documentation.
All of the Selenium components change quite fast over time, so this might cause the documentation to be out of date. If you find this to be the case, as mentioned, don’t hesitate to create an issue for that. It also might be possible that you know how to bring up to date the documentation, so please send us a pull request with the related changes.
If you are not sure about what you have found is an issue or not, please ask through the communication channels described at https://selenium.dev/support.
The Selenium project welcomes new contributors. Individuals making significant and valuable contributions over time are made Committers and given commit-access to the project.
This guide will guide you through the contribution process.
Step 1: Fork
Fork the project on Github and check out your copy locally.
% git clone firstname.lastname@example.org:seleniumhq/seleniumhq.github.io.git % cd seleniumhq.github.io
Please follow the Install Hugo instructions from Docsy.
Step 2: Branch
Create a feature branch and start hacking:
% git checkout -b my-feature-branch
We practice HEAD-based development, which means all changes are applied
directly on top of
Step 3: Make changes
The repository contains the site and docs. Before jumping into
making changes, please initialize the submodules and install the
needed dependencies (see commands below). To make changes to the site,
work on the
website_and_docs directory. To see a live preview of
your changes, run
hugo server on the site’s root directory.
% git submodule update --init --recursive % cd website_and_docs % hugo server
See Style Guide for more information on our conventions for contribution
Step 4: Commit
First make sure git knows your name and email address:
% git config --global user.name 'Santa Claus' % git config --global user.email 'email@example.com'
Writing good commit messages is important. A commit message should describe what changed, why, and reference issues fixed (if any). Follow these guidelines when writing one:
- The first line should be around 50 characters or less and contain a short description of the change.
- Keep the second line blank.
- Wrap all other lines at 72 columns.
Fixes #N, where N is the issue number the commit fixes, if any.
A good commit message can look like this:
explain commit normatively in one line Body of commit message is a few lines of text, explaining things in more detail, possibly giving some background about the issue being fixed, etc. The body of the commit message can be several paragraphs, and please do proper word-wrap and keep columns shorter than about 72 characters or so. That way `git log` will show things nicely even when it is indented. Fixes #141
The first line must be meaningful as it’s what people see when they
git shortlog or
git log --oneline.
Step 5: Rebase
git rebase (not
git merge) to sync your work from time to time.
% git fetch origin % git rebase origin/trunk
Step 6: Test
Always remember to run the local server, with this you can be sure that your changes have not broken anything.
Step 7: Push
% git push origin my-feature-branch
Go to https://github.com/yourusername/seleniumhq.github.io.git and press the Pull Request and fill out the form. Please indicate that you’ve signed the CLA (see Step 7).
Pull requests are usually reviewed within a few days. If there are comments to address, apply your changes in new commits (preferably fixups) and push to the same branch.
Step 8: Integration
When code review is complete, a committer will take your PR and integrate it on the repository’s trunk branch. Because we like to keep a linear history on the trunk branch, we will normally squash and rebase your branch history.
All details on how to communicate with the project contributors and the community overall can be found at https://selenium.dev/support