| commit | 6ed67cb70ec5f4393eb45e02a898d35cee6e9b98 | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Wed Jul 13 08:16:11 2022 -0500 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Thu Aug 11 18:30:07 2022 +0000 |
| tree | 53fb2891ea41b02e2e979a8cc5d0ffab791458a1 | |
| parent | a9199a499889400fbc76c04968df6af2c19400c2 [diff] |
Revert "Allow script to be used without a git alias"
This reverts commit 6b4b9df44144c1cc2072eb1847a9fb335d326710.
The change switches from using an SSH alias to using a direct
hostname / port argument in the claims that it is better for most
users, but it is not.
- The original 'openbmc.gerrit' SSH alias has been documented
forever in openbmc/docs:CONTRIBUTING.md and it is expected that
everyone has it set up as it is part of our gerrit documentation.
- Almost no one runs their system with their Unix ID matching their
Github ID, which means the SSH also needs a username argument
in order to be useful for most people (which was not added by
this previous commit).
As we already document having some kind of SSH alias for interacting
with Gerrit, using an SSH alias is necessary for the majority of users
anyhow, and the SSH alias chosen by default is the project-wide
documented suggestion, I am reverting this back to the previous
behavior.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I78947c75ce689d443d2b08475a35328be296784b
The goal of this repository is to collect the two-minute hacks you write to automate interactions with OpenBMC systems.
It's highly likely the scripts don't meet your needs - they could be undocumented, dysfunctional or utterly broken. Please help us improve!
Then this repository aims to be the default destination for your otherwise un-homed scripts. As such we are setting the bar for submission pretty low, and we aim to make the process as easy as possible.
Please use gerrit for all patches to this repository:
Do note that you will need to be party to the OpenBMC CLA before your contributions can be accepted. See Gerrit Setup and CLA for more information.
So long as your patches look sane with a cursory glance you can expect them to be applied. We may push back in the event that similar tools already exist or there are egregious issues.
We don't ask for much, but you need to give us at least a Signed-off-by, use SPDX markers in your source files and put your work under an Apache 2.0 compatible license.
There's no standard way to install the scripts housed here, and adding parts of the repository to your PATH might be a bit of a dice-roll. We may also move or remove scripts from time to time as part of housekeeping. It's probably best to copy things out if you need stability.