Skip to content

feat: github integration #122

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.

Sign up for GitHub

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

Merged
paul58914080 merged 9 commits into from
Jan 20, 2026
Merged

feat: github integration #122

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
9 commits
Select commit Hold shift + click to select a range
7ece0a6
docs: add LICENSE
paul58914080 Jan 20, 2026
9008d6e
docs(github): migrate to ISSUE_TEMPLATE
paul58914080 Jan 20, 2026
37048d3
docs(github): add CODEOWNERS
paul58914080 Jan 20, 2026
aa0dbbd
docs(github): add CONTRIBUTING
paul58914080 Jan 20, 2026
c9637ef
docs(github): add dependabot
paul58914080 Jan 20, 2026
476891d
docs(github): add PULL_REQUEST_TEMPLATE
paul58914080 Jan 20, 2026
e4a42ae
ci: add build workflow
paul58914080 Jan 20, 2026
38de7d6
ci: add release workflow
paul58914080 Jan 20, 2026
155402f
ci: update java-version to 11
paul58914080 Jan 20, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .github/CODEOWNERS
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
* @societe-generale/gbis-core @vincent-fuchs
88 changes: 88 additions & 0 deletions .github/CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,88 @@
# How to contribute

We are really glad you're reading this, because we need volunteer developers to help this project
come to fruition. We welcome you to contribute to our projects
at [Société Générale](https://github.com/societe-generale) and help make it even better than it is
today!

When contributing to this repository, please first discuss the change you wish to make via issues or
pull requests.

Please note we have a code of conduct, please follow it in all your interactions with the project.

## Pull request process

- Ensure you have performed a self-review of your changes
- Ensure the new changes generate no new warnings
- Ensure you have added tests that prove the fix is effective or that the feature works
- Ensure new and existing unit tests pass locally with my changes
Copy link

Copilot AI Jan 20, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Inconsistent pronoun usage. The text reads "with my changes" but should be "with your changes" to maintain consistency with the second-person perspective used throughout the contributing guidelines.

Suggested change
- Ensure new and existing unit tests pass locally with my changes
- Ensure new and existing unit tests pass locally with your changes

Copilot uses AI. Check for mistakes.
- Ensure your commit message should
follow [conventional commit message guidelines](https://www.conventionalcommits.org/en/v1.0.0/)
Comment on lines +19 to +20
Copy link

Copilot AI Jan 20, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awkward sentence structure. The phrase "Ensure your commit message should follow" contains redundant auxiliary verbs. It should be either "Ensure your commit message follows" or "Your commit message should follow" to improve clarity and grammatical correctness.

Suggested change
- Ensure your commit message should
follow [conventional commit message guidelines](https://www.conventionalcommits.org/en/v1.0.0/)
- Ensure your commit message follows [conventional commit message guidelines](https://www.conventionalcommits.org/en/v1.0.0/)

Copilot uses AI. Check for mistakes.

## Code of Conduct

### Our pledge

In the interest of fostering an open and welcoming environment, we as
contributors and maintainers pledge to making participation in our project and
our community a harassment-free experience for everyone, regardless of age, body
size, disability, ethnicity, gender identity and expression, level of experience,
nationality, personal appearance, race, religion, or sexual identity and
orientation.

### Our standards

Examples of behavior that contributes to creating a positive environment
include:

* Using welcoming and inclusive language
* Being respectful of differing viewpoints and experiences
* Gracefully accepting constructive criticism
* Focusing on what is best for the community
* Showing empathy towards other community members

Examples of unacceptable behavior by participants include:

* The use of sexualized language or imagery and unwelcome sexual attention or
advances
* Trolling, insulting/derogatory comments, and personal or political attacks
* Public or private harassment
* Publishing others' private information, such as a physical or electronic
address, without explicit permission
* Other conduct which could reasonably be considered inappropriate in a
professional setting

### Our responsibilities

Project maintainers are responsible for clarifying the standards of acceptable
behavior and are expected to take appropriate and fair corrective action in
response to any instances of unacceptable behavior.

Project maintainers have the right and responsibility to remove, edit, or
reject comments, commits, code, wiki edits, issues, and other contributions
that are not aligned to this Code of Conduct, or to ban temporarily or
permanently any contributor for other behaviors that they deem inappropriate,
threatening, offensive, or harmful.

### Scope

This Code of Conduct applies both within project spaces and in public spaces
when an individual is representing the project or its community. Examples of
representing a project or community include using an official project e-mail
address, posting via an official social media account, or acting as an appointed
representative at an online or offline event. Representation of a project may be
further defined and clarified by project maintainers.

### Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be
reported by contacting the project team at [opensource@socgen.com](mailto:opensource@socgen.com).
All
complaints will be reviewed and investigated and will result in a response that
is deemed necessary and appropriate to the circumstances. The project team is
obligated to maintain confidentiality with regard to the reporter of an incident.
Further details of specific enforcement policies may be posted separately.

Project maintainers who do not follow or enforce the Code of Conduct in good
faith may face temporary or permanent repercussions as determined by other
members of the project's leadership.
43 changes: 0 additions & 43 deletions .github/ISSUE_TEMPLATE.md
View file
Open in desktop

This file was deleted.

74 changes: 74 additions & 0 deletions .github/ISSUE_TEMPLATE/bug_report.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,74 @@
name: "Bug report"
description: "Report a reproducible bug."
title: "[Bug] {{summary}}"
Copy link

Copilot AI Jan 20, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The title field uses {{summary}} interpolation syntax, but GitHub issue forms do not support variable interpolation in the title field. The title field must be a static string. Users can edit the title after the issue is created, but you cannot programmatically insert values from form fields into it. Consider using a static title like "[Bug] " and let users complete it, or remove the variable placeholder.

Suggested change
title: "[Bug] {{summary}}"
title: "[Bug]"

Copilot uses AI. Check for mistakes.
type: bug
Copy link

Copilot AI Jan 20, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The type: field is not a valid top-level field in GitHub issue form syntax. GitHub issue forms only support name, description, title, labels, assignees, and body at the top level. This field should be removed as it will cause the issue template to fail validation.

Suggested change
type: bug

Copilot uses AI. Check for mistakes.
assignees:
- vincent-fuchs
- paul58914080
labels:
- bug
- needs-triage
body:
- type: input
id: summary
attributes:
label: Summary
description: "Short, descriptive summary of the bug."
placeholder: "Brief summary (<=120 chars)"
validations:
required: true
max_length: 120
Copy link

Copilot AI Jan 20, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The validation field max_length is not a valid validation option for input elements in GitHub issue forms. Input elements only support the required validation option. If you want to enforce character limits, this should be mentioned in the description or placeholder text instead, as GitHub issue forms do not provide native max length validation for input fields.

Suggested change
max_length: 120

Copilot uses AI. Check for mistakes.
- type: textarea
id: environment
attributes:
label: Environment
description: "Provide versions and environment details (e.g. Version, OS, JVM)."
placeholder: "Version: \nOS: \nJVM:"
validations:
required: false
- type: textarea
id: current_behavior
attributes:
label: Current behavior
description: "Describe what actually happens and include relevant logs or stack traces."
placeholder: "What happens now? Include logs or errors"
validations:
required: true
- type: textarea
id: expected_behavior
attributes:
label: Expected behavior
description: "Describe what you expected to happen."
placeholder: "What should happen instead?"
validations:
required: true
- type: textarea
id: steps_to_reproduce
attributes:
label: Steps to reproduce
description: "Step-by-step instructions to reproduce the bug. Exact commands, inputs, or links help a lot."
placeholder: "1) ...\n2) ...\n3) ..."
validations:
required: true
- type: checkboxes
id: attachments
attributes:
label: Additional information (optional)
description: "Optional: check items you can attach to help triage."
options:
- label: I can provide logs
required: false
- label: I can provide a small reproduction repository
required: false
- label: I can provide screenshots
required: false
validations:
required: false
- type: input
id: contact
attributes:
label: Contact (optional)
description: "Optional: your GitHub handle / email / link to more details."
placeholder: "@your-handle, email, or link"
validations:
required: false
2 changes: 2 additions & 0 deletions .github/ISSUE_TEMPLATE/config.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
blank_issues_enabled: false

53 changes: 53 additions & 0 deletions .github/ISSUE_TEMPLATE/feature_request.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,53 @@
name: "Feature request"
description: "Suggest a new feature or an improvement."
title: "[Feature] {{summary}}"
Copy link

Copilot AI Jan 20, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The title field uses {{summary}} interpolation syntax, but GitHub issue forms do not support variable interpolation in the title field. The title field must be a static string. Users can edit the title after the issue is created, but you cannot programmatically insert values from form fields into it. Consider using a static title like "[Feature] " and let users complete it, or remove the variable placeholder.

Suggested change
title: "[Feature] {{summary}}"
title: "[Feature] "

Copilot uses AI. Check for mistakes.
type: feature
Copy link

Copilot AI Jan 20, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The type: field is not a valid top-level field in GitHub issue form syntax. GitHub issue forms only support name, description, title, labels, assignees, and body at the top level. This field should be removed as it will cause the issue template to fail validation.

Suggested change
type: feature

Copilot uses AI. Check for mistakes.
assignees:
- vincent-fuchs
- paul58914080
labels:
- enhancement
- needs-triage
body:
- type: input
id: summary
attributes:
label: Summary
description: "Short, descriptive summary of the requested feature."
placeholder: "Brief summary (<=120 chars)"
validations:
required: true
max_length: 120
Copy link

Copilot AI Jan 20, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The validation field max_length is not a valid validation option for input elements in GitHub issue forms. Input elements only support the required validation option. If you want to enforce character limits, this should be mentioned in the description or placeholder text instead, as GitHub issue forms do not provide native max length validation for input fields.

Suggested change
max_length: 120

Copilot uses AI. Check for mistakes.
- type: textarea
id: motivation
attributes:
label: Motivation
description: "Why is this feature important? What problems does it solve?"
placeholder: "Why do you want this?"
validations:
required: true
- type: textarea
id: proposed_behavior
attributes:
label: Proposed behavior / API
description: "Describe the desired behavior. Give examples or pseudo-code if helpful."
placeholder: "Describe how the feature should behave."
validations:
required: true
- type: textarea
id: acceptance_criteria
attributes:
label: Acceptance criteria (optional)
description: "Optional: define measurable acceptance criteria for the feature."
placeholder: "e.g. 'When X, then Y should happen'"
validations:
required: false
- type: input
id: contact
attributes:
label: Contact (optional)
description: "Optional: your GitHub handle / email / link to more details."
placeholder: "@your-handle, email, or link"
validations:
required: false

45 changes: 45 additions & 0 deletions .github/ISSUE_TEMPLATE/question.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,45 @@
name: "Question"
description: "Ask a question about how to use the project, APIs or docs."
title: "[Question] {{summary}}"
Copy link

Copilot AI Jan 20, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The title field uses {{summary}} interpolation syntax, but GitHub issue forms do not support variable interpolation in the title field. The title field must be a static string. Users can edit the title after the issue is created, but you cannot programmatically insert values from form fields into it. Consider using a static title like "[Question] " and let users complete it, or remove the variable placeholder.

Suggested change
title: "[Question] {{summary}}"
title: "[Question]"

Copilot uses AI. Check for mistakes.
type: question
Copy link

Copilot AI Jan 20, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The type: field is not a valid top-level field in GitHub issue form syntax. GitHub issue forms only support name, description, title, labels, assignees, and body at the top level. This field should be removed as it will cause the issue template to fail validation.

Suggested change
type: question

Copilot uses AI. Check for mistakes.
assignees:
- vincent-fuchs
- paul58914080
labels:
- question
- needs-triage
body:
- type: input
id: summary
attributes:
label: Summary
description: "Short summary of your question."
placeholder: "Brief summary (<=120 chars)"
validations:
required: true
max_length: 120
Copy link

Copilot AI Jan 20, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The validation field max_length is not a valid validation option for input elements in GitHub issue forms. Input elements only support the required validation option. If you want to enforce character limits, this should be mentioned in the description or placeholder text instead, as GitHub issue forms do not provide native max length validation for input fields.

Suggested change
max_length: 120

Copilot uses AI. Check for mistakes.
- type: textarea
id: details
attributes:
label: Details
description: "Explain your question in detail and what you've tried so far."
placeholder: "Provide context, code snippets, or links to docs."
validations:
required: true
- type: textarea
id: environment
attributes:
label: Your environment (optional)
description: "Optional: provide version, OS, or library versions if relevant."
placeholder: "Version: \nOS: \nLibraries:"
validations:
required: false
- type: input
id: contact
attributes:
label: Contact (optional)
description: "Optional: your GitHub handle / email / link to more details."
placeholder: "@your-handle, email, or link"
validations:
required: false

15 changes: 3 additions & 12 deletions .github/PULL_REQUEST_TEMPLATE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,17 +1,8 @@
## Summary

<!-- Provide a general summary description of your changes -->

## Details

<!-- Describe your changes in detail -->

## Context

<!-- Why is this change required? What problem does it solve? -->
<!-- Which environnment is/are impacted ? -->

## Checklist:
## Checklist

<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
Expand All @@ -20,5 +11,5 @@
- [ ] Documentation has been updated accordingly to this PR


## Related issue :
<!-- If it fixes an open issue, please link to the issue here. -->
## Related issue
<!-- If it fixes an open issue, please link to the issue here. -->
22 changes: 22 additions & 0 deletions .github/dependabot.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
version: 2
updates:
- package-ecosystem: maven
directory: "/"
schedule:
interval: daily
open-pull-requests-limit: 10
labels:
- dependencies
- automated
commit-message:
prefix: "build: "
- package-ecosystem: github-actions
directory: "/.github/"
Copy link

Copilot AI Jan 20, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The directory path for the github-actions package ecosystem should be "/" not "/.github/". GitHub Actions workflows are typically located in .github/workflows, but Dependabot expects the directory to be set to "/" to monitor all GitHub Actions in the repository. This incorrect path will prevent Dependabot from detecting and updating GitHub Actions dependencies.

Suggested change
directory: "/.github/"
directory: "/"

Copilot uses AI. Check for mistakes.
schedule:
interval: weekly
open-pull-requests-limit: 5
labels:
- ci
- automated
commit-message:
prefix: "ci: "
Loading