hasura/graphql-engine
1
0
Fork 0
mirror of https://github.com/hasura/graphql-engine.git synced 2024-12-15 09:22:43 +03:00
Code Issues Projects Releases Wiki Activity
54125f2ae6
graphql-engine/Makefile

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

18 lines
470 B
Makefile
Raw Normal View History

Fun improvements to Makefiles, with the intent of re-using test-infrastructure.mk. I intend to use the Make targets around starting and stopping backend databases in order to wrap the Python integration tests in targets. To that end, I have: 1. Factored out test infrastructure targets into _test-infrastructure.mk_. 2. Actually run the functions from _util.sh_; previously we were just running a bash script with no explicit commands. _util.sh_ must be `source`d and then you invoke the relevant function. 3. Run `docker-compose` through Nix if possible. PR-URL: https://github.com/hasura/graphql-engine-mono/pull/5136 GitOrigin-RevId: d7a01958045a82199c969ec3f88387d7d76d254b
2022-07-22 13:56:03 +03:00
SHELL := bash -e -u -o pipefail
server, CI: use ormolu as a formatter for Haskell sources ### Description - sets up a Makefile target for running ormolu to format and check source code - updates CI to run ormolu instead of stylish-haskell (and to check instead of format actively) Compare #1679. Here's the plan for merging this: 1. merge this PR; at this point, all PRs will fail CI unless they have the `ignore-server-format-checks` label set 2. merge follow-up PR #2404 that does nothing but actually reformats the codebase 3. tag the merge commit as `post-ormolu` (also on `graphql-engine`, for the benefits of community contributors) 4. provide the following script to any devs in order to update their branches: ``` $ git checkout my-feature-branch $ git merge post-ormolu^ $ make format $ git commit -a -m "reformat with ormolu" $ git merge -s ours post-ormolu ``` (I'll put this in the commit message) https://github.com/hasura/graphql-engine-mono/pull/2020 Co-authored-by: Philip Lykke Carlsen <358550+plcplc@users.noreply.github.com> Co-authored-by: Swann Moreau <62569634+evertedsphere@users.noreply.github.com> GitOrigin-RevId: 130f480a6d79967c8d045b7f3a6dec30b10472a7
2021-09-24 00:22:27 +03:00
# default target
.PHONY: help
## help: prints help message
help:
@echo "Usage:"
@sed -n 's/^##//p' ${MAKEFILE_LIST} | column -t -s ':' | sed -e 's/^/ /'
tooling: Add `make build...` commands PR-URL: https://github.com/hasura/graphql-engine-mono/pull/4824 GitOrigin-RevId: eeee7c47fb8b8160d85aee2d9d07fdf9ed14a703
2022-07-04 14:44:15 +03:00
include ./scripts/make/build.mk
[tooling] `make` commands for building and formatting CI pipeline PR-URL: https://github.com/hasura/graphql-engine-mono/pull/7051 GitOrigin-RevId: dca45b31608680bf57a2dd190171b2567e1fcb02
2022-11-25 18:44:04 +03:00
include ./scripts/make/ci.mk
include ./scripts/make/ghcid.mk
include ./scripts/make/legacy-tests.mk
Fun improvements to Makefiles, with the intent of re-using test-infrastructure.mk. I intend to use the Make targets around starting and stopping backend databases in order to wrap the Python integration tests in targets. To that end, I have: 1. Factored out test infrastructure targets into _test-infrastructure.mk_. 2. Actually run the functions from _util.sh_; previously we were just running a bash script with no explicit commands. _util.sh_ must be `source`d and then you invoke the relevant function. 3. Run `docker-compose` through Nix if possible. PR-URL: https://github.com/hasura/graphql-engine-mono/pull/5136 GitOrigin-RevId: d7a01958045a82199c969ec3f88387d7d76d254b
2022-07-22 13:56:03 +03:00
include ./scripts/make/lint.mk
server: commit Metadata OpenAPI spec with CI check, add Typescript client scaffolding ## Description Adds `metadata.openapi.json` to version control. Adds a Buildkite job that verifies the spec is up-to-date on server changes, and fails the CI pipeline if not. Adds scaffolding for a new Typescript project that consumes that OpenAPI spec, and produces Typescript types. This is adapted from the similar existing data connectors project in `dc-agents/dc-api-types/`. Generated code is *not* committed to version control. Instead there is a script to generate code on-demand at publishing time. There are plans to incorporate publishing the generated project to NPM using a forthcoming pipeline that the Console team is working on. For the moment the Typescript project is under `metadata-api-types/typescript/`. The plan is to move the project in a future PR to the frontend sub-monorepo. PR-URL: https://github.com/hasura/graphql-engine-mono/pull/7525 GitOrigin-RevId: dc27a807e52af117636f3aa6c2c289a0be87ade1
2023-02-15 21:36:25 +03:00
include ./scripts/make/metadata-api.mk
Fun improvements to Makefiles, with the intent of re-using test-infrastructure.mk. I intend to use the Make targets around starting and stopping backend databases in order to wrap the Python integration tests in targets. To that end, I have: 1. Factored out test infrastructure targets into _test-infrastructure.mk_. 2. Actually run the functions from _util.sh_; previously we were just running a bash script with no explicit commands. _util.sh_ must be `source`d and then you invoke the relevant function. 3. Run `docker-compose` through Nix if possible. PR-URL: https://github.com/hasura/graphql-engine-mono/pull/5136 GitOrigin-RevId: d7a01958045a82199c969ec3f88387d7d76d254b
2022-07-22 13:56:03 +03:00
include ./scripts/make/tests.mk
[tooling] `make` commands for building and formatting CI pipeline PR-URL: https://github.com/hasura/graphql-engine-mono/pull/7051 GitOrigin-RevId: dca45b31608680bf57a2dd190171b2567e1fcb02
2022-11-25 18:44:04 +03:00
include ./scripts/make/test-infrastructure.mk
Reference in New Issue Copy Permalink