python/httpie-cli
1
0
Fork 0
mirror of https://github.com/httpie/cli.git synced 2026-06-20 11:32:56 +02:00
Code Activity

Rename repo from httpie/httpie to httpie/cli

Browse Source
This commit is contained in:
Jakub Roztocil
2023-08-06 14:04:32 +02:00
parent 30a6f73ec8
commit 011402152c
40 changed files with 220 additions and 220 deletions
Download Patch File Download Diff File Expand all files Collapse all files
extras/man/http.1
+1 -1
View File
@@ -597,4 +597,4 @@ For every \fB\,--OPTION\/\fR there is also a \fB\,--no-OPTION\/\fR that reverts
to its default value.
Suggestions and bug reports are greatly appreciated:
https://github.com/httpie/httpie/issues
https://github.com/httpie/cli/issues
extras/man/https.1
+1 -1
View File
@@ -597,4 +597,4 @@ For every \fB\,--OPTION\/\fR there is also a \fB\,--no-OPTION\/\fR that reverts
to its default value.
Suggestions and bug reports are greatly appreciated:
https://github.com/httpie/httpie/issues
https://github.com/httpie/cli/issues
extras/packaging/linux/README.md
+3 -3
View File
@@ -7,13 +7,13 @@ This directory contains the build scripts for creating:
- A self-contained binary executable for the HTTPie itself
- `httpie.deb` and `httpie.rpm` packages for Debian and Fedora.
The process of constructing them are fully automated, and can be easily done through the [`Release as Standalone Linux Package`](https://github.com/httpie/httpie/actions/workflows/release-linux-standalone.yml)
The process of constructing them are fully automated, and can be easily done through the [`Release as Standalone Linux Package`](https://github.com/httpie/cli/actions/workflows/release-linux-standalone.yml)
action. Once it finishes, the release artifacts will be attached in the summary page of the triggered run.
## Hacking
The main entry point for the package builder is the [`build.py`](https://github.com/httpie/httpie/blob/master/extras/packaging/linux/build.py). It
The main entry point for the package builder is the [`build.py`](https://github.com/httpie/cli/blob/master/extras/packaging/linux/build.py). It
contains 2 major methods:
- `build_binaries`, for the self-contained executables
@@ -39,7 +39,7 @@ Since the `httpie` depends on having a pip executable, we explicitly depend on t
### Docker Image
This directory also contains a [docker image](https://github.com/httpie/httpie/blob/master/extras/packaging/linux/Dockerfile) which helps
This directory also contains a [docker image](https://github.com/httpie/cli/blob/master/extras/packaging/linux/Dockerfile) which helps
building our standalone binaries in an isolated environment with the lowest possible library versions. This is important, since even though
the executables are standalone they still depend on some main system C libraries (like `glibc`) so we need to create our executables inside
an environment with a very old (but not deprecated) glibc version. It makes us soundproof for all active Ubuntu/Debian versions.
extras/profiling/README.md
+1 -1
View File
@@ -28,7 +28,7 @@ on both of them. It will compare the results and print it as a markdown table:
| Geometric mean | (ref) | 1.10x faster |
If your `master` branch is not up-to-date, you can get a fresh clone by passing
`--fresh` option. This way, the benchmark runner will clone the `httpie/httpie`
`--fresh` option. This way, the benchmark runner will clone the `httpie/cli`
repo from `GitHub` and use it as the baseline.
You can customize these branches by passing `--local-repo`/`--target-branch`,
extras/profiling/run.py
+1 -1
View File
@@ -50,7 +50,7 @@ from typing import (IO, Dict, Generator, Iterable, List, Optional,
BENCHMARK_SCRIPT = Path(__file__).parent / 'benchmarks.py'
CURRENT_REPO = Path(__file__).parent.parent.parent
GITHUB_URL = 'https://github.com/httpie/httpie.git'
GITHUB_URL = 'https://github.com/httpie/cli.git'
TARGET_BRANCH = 'master'
# Additional dependencies for --complex