Skip to content

Commit 6781ab9

Browse files
authored
Merge pull request #2 from DataFog/dev
Dev
2 parents 5191c42 + 2b47d3d commit 6781ab9

38 files changed

Lines changed: 1700 additions & 447 deletions

.github/workflows/main-cicd.yml

Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -40,3 +40,35 @@ jobs:
4040
govulncheck ./...
4141
- name: Build container image
4242
run: docker build . --file Dockerfile --tag datafog-api:$(date +%s)
43+
44+
benchmark:
45+
runs-on: ubuntu-latest
46+
needs: build
47+
steps:
48+
- uses: actions/checkout@v4
49+
- name: Set up Go
50+
uses: actions/setup-go@v5
51+
with:
52+
go-version: "1.24.13"
53+
- name: Run benchmark suites with trend report
54+
run: |
55+
bash scripts/run-benchmarks.sh
56+
- name: Upload benchmark artifacts
57+
uses: actions/upload-artifact@v4
58+
with:
59+
name: benchmark-results
60+
path: |
61+
/tmp/bench/benchmark-current.txt
62+
/tmp/bench/benchmark-trend.txt
63+
64+
race:
65+
runs-on: ubuntu-latest
66+
needs: build
67+
steps:
68+
- uses: actions/checkout@v4
69+
- name: Set up Go
70+
uses: actions/setup-go@v5
71+
with:
72+
go-version: "1.24.13"
73+
- name: Run race detector
74+
run: go test -race ./...

CONTRIBUTING.md

Lines changed: 9 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,12 @@
1-
# datafog contributing guidelines
1+
# Contributing to DataFog
22

3-
The datafog community appreciates your contributions via issues and
4-
pull requests. Note that the [code of conduct](CODE_OF_CONDUCT.md)
5-
applies to all interactions with the datafog project, including
6-
issues and pull requests.
3+
DataFog welcomes contributions via issues and pull requests. The [Code of Conduct](CODE_OF_CONDUCT.md) applies to all project interactions, including issues and PRs.
4+
5+
When submitting a pull request:
6+
7+
- Follow project style guidelines.
8+
- Ensure tests and docs are updated where behavior changes.
9+
- Keep commit messages clear and descriptive.
10+
- Confirm your work is covered by a compatible license in line with the project [`LICENSE`](LICENSE).
711

8-
When submitting pull requests, please follow the style guidelines of
9-
the project, ensure that your code is tested and documented, and write
10-
good commit messages, e.g., following [these
11-
guidelines](https://chris.beams.io/posts/git-commit/).
1212

13-
By submitting a pull request, you are licensing your code under the
14-
project [license](LICENSE) and affirming that you either own copyright
15-
(automatic for most individuals) or are authorized to distribute under
16-
the project license (e.g., in case your employer retains copyright on
17-
your work).

0 commit comments

Comments
 (0)