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

Add contributing guidelines for the repository #2

Merged
merged 2 commits into from
Apr 18, 2024

Conversation

0237h
Copy link
Collaborator

@0237h 0237h commented Apr 18, 2024

Explaining the repository structure and how to contribute through the CONTRIBUTING.md file.

@0237h 0237h self-assigned this Apr 18, 2024
@github-actions github-actions bot added documentation Improvements or additions to documentation ops Related to repository operations labels Apr 18, 2024
@0237h 0237h merged commit 2da29ba into develop Apr 18, 2024
2 checks passed
@0237h 0237h deleted the docs/contributing-guidelines branch April 18, 2024 20:16
0237h added a commit that referenced this pull request Apr 19, 2024
* Make Release Drafter follow `develop` branch

* Add CONTRIBUTING.md and update README.md
0237h added a commit that referenced this pull request Apr 22, 2024
* Make workflow separate `develop` from `release` tags for artifact builds

* Add comments and replace `console` log

* Add contributing guidelines for the repository (#2)

* Make Release Drafter follow `develop` branch

* Add CONTRIBUTING.md and update README.md

* Results pagination overhaul (#3)

* Replace `offset` parameter with `page` for pagination of results

Instead of taking the offset directly from the user query, we can
compute it by multiplying the page number with the `limit` parameter
set in the query or by default.

Not having a `page` parameter in the query is equivalent to `page=1`.

* Fix `limit <= 0` and add missing tests

* Add `parsePage` tests

* Add metadata information to API responses

The metadata contains information for the pagination of results.
The following fields are available:
- `next_page`, capped to `total_pages` on reaching the last page
- `previous_page`, set to 1 on the first page
- `total_pages`, computed from the `limit` parameter
- `total_results` returned from `rows_before_limit_at_least` of
   ClickHouse's response
   (https://clickhouse.com/docs/en/interfaces/formats#json)

* Make `limit` parameter default to `config.maxLimit`

Resolves #1

* Edit automation and documentation to drop `develop` (#4)

Given the relatively small size of the repo, it will be easier to use
to make PRs directly to the `main` branch, keeping the current tagging
schema intact.

PRs would still be required before merging to `main` following the
conventions described in `CONTRIBUTING.md`.
0237h added a commit that referenced this pull request Apr 22, 2024
* Make workflow separate `develop` from `release` tags for artifact builds

* Add comments and replace `console` log

* Add contributing guidelines for the repository (#2)

* Make Release Drafter follow `develop` branch

* Add CONTRIBUTING.md and update README.md

* Results pagination overhaul (#3)

* Replace `offset` parameter with `page` for pagination of results

Instead of taking the offset directly from the user query, we can
compute it by multiplying the page number with the `limit` parameter
set in the query or by default.

Not having a `page` parameter in the query is equivalent to `page=1`.

* Fix `limit <= 0` and add missing tests

* Add `parsePage` tests

* Add metadata information to API responses

The metadata contains information for the pagination of results.
The following fields are available:
- `next_page`, capped to `total_pages` on reaching the last page
- `previous_page`, set to 1 on the first page
- `total_pages`, computed from the `limit` parameter
- `total_results` returned from `rows_before_limit_at_least` of
   ClickHouse's response
   (https://clickhouse.com/docs/en/interfaces/formats#json)

* Make `limit` parameter default to `config.maxLimit`

Resolves #1

* Edit automation and documentation to drop `develop` (#4)

Given the relatively small size of the repo, it will be easier to use
to make PRs directly to the `main` branch, keeping the current tagging
schema intact.

PRs would still be required before merging to `main` following the
conventions described in `CONTRIBUTING.md`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation ops Related to repository operations
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant