Skip to content

Commit

Permalink
Update repo metadata
Browse files Browse the repository at this point in the history
  • Loading branch information
Virtlink committed Aug 1, 2024
1 parent b94ec97 commit f020bab
Show file tree
Hide file tree
Showing 10 changed files with 609 additions and 251 deletions.
15 changes: 12 additions & 3 deletions .github/workflows/build.yaml
Original file line number Diff line number Diff line change
@@ -1,4 +1,8 @@
---
# !! THIS FILE WAS GENERATED USING repoman !!
# Modify `repo.yaml` instead and use `repoman` to update this file
# See: https://github.com/metaborg/metaborg-gradle/

name: 'Build & Publish'

on: # yamllint disable-line rule:truthy
Expand All @@ -10,26 +14,31 @@ on: # yamllint disable-line rule:truthy
jobs:
build:
uses: metaborg/actions/.github/workflows/gradle-build-matrix.yaml@main
with:
gradle-command: |
gradle build
# Publish snapshots
publish-snapshot:
uses: metaborg/actions/.github/workflows/gradle-publish.yaml@main
with:
gradle-command: |
gradle :publish -Pgitonium.isSnapshot=true
gradle publish -Pgitonium.isSnapshot=true
gradle-version-command: |
gradle -q :printVersion -Pgitonium.isSnapshot=true
if: "github.event_name == 'push' && github.ref == 'refs/heads/master'"
needs: [build]
secrets:
METABORG_ARTIFACTS_USERNAME: ${{ secrets.METABORG_ARTIFACTS_USERNAME }}
METABORG_ARTIFACTS_PASSWORD: ${{ secrets.METABORG_ARTIFACTS_PASSWORD }}
# Publish releases
publish-release:
uses: metaborg/actions/.github/workflows/gradle-publish.yaml@main
with:
gradle-command: |
gradle :publish
gradle publish
gradle-version-command: |
gradle -q :printVersion
if: "github.event_name == 'push' && startsWith(github.ref, 'refs/tags/release-')"
if: "github.event_name == 'push' && startsWith(github.ref, 'refs/tags/devenv-release/')"
needs: [build]
secrets:
METABORG_ARTIFACTS_USERNAME: ${{ secrets.METABORG_ARTIFACTS_USERNAME }}
Expand Down
103 changes: 74 additions & 29 deletions .gitignore
Original file line number Diff line number Diff line change
@@ -1,35 +1,80 @@
# macOS
*.DS_Store
# !! THIS FILE WAS GENERATED USING repoman !!
# Modify `repo.yaml` instead and use `repoman` to update this file
# See: https://github.com/metaborg/metaborg-gradle/

# Java
*.class
*.log
*.jar
*.war
*.nar
*.ear


# Gradle
**/.gradle
**/build/
.gradle
build/
!gradle/wrapper/gradle-wrapper.jar
!**/src/main/**/build/
!**/src/test/**/build/


# IntelliJ
**/.idea
**/out
.idea/*
!.idea/icon.svg
!.idea/icon_dark.svg
*.iws
out/
*.iml
*.ipr
!**/src/main/**/out/
!**/src/test/**/out/


# Eclipse
**/.project
**/.settings
**/.classpath
**/.factorypath
**/bin

# Python
__pycache__/
*.py[cod]
*$py.class
*.so
.python-version
.env/
.venv/
env/
venv/
ENV/
env.bak/
venv.bak/
pythonenv*
/site/
build/
*.egg-info/
.metadata
.classpath
.project
.apt_generated
.settings
.springBeans
.sts4-cache
bin/
tmp/
*.tmp
*.bak
*.swp
*~.nib
local.properties
.settings/
.loadpath
.recommenders
.factorypath
.recommenders/
.apt_generated/
.apt_generated_test/
!**/src/main/**/bin/
!**/src/test/**/bin/


# NetBeans
/nbproject/private/
/nbbuild/
/dist/
/nbdist/
/.nb-gradle/


# VS Code
.vscode/

# Misc
.cache
.DS_Store
*.lock
jte-classes/

# Spoofax
src-gen/
target/

133 changes: 133 additions & 0 deletions CODE_OF_CONDUCT.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,133 @@
# Contributor Covenant Code of Conduct

## Our Pledge

We as members, contributors, and leaders pledge to make participation in our
community a harassment-free experience for everyone, regardless of age, body
size, visible or invisible disability, ethnicity, sex characteristics, gender
identity and expression, level of experience, education, socio-economic status,
nationality, personal appearance, race, caste, color, religion, or sexual
identity and orientation.

We pledge to act and interact in ways that contribute to an open, welcoming,
diverse, inclusive, and healthy community.

## Our Standards

Examples of behavior that contributes to a positive environment for our
community include:

* Demonstrating empathy and kindness toward other people
* Being respectful of differing opinions, viewpoints, and experiences
* Giving and gracefully accepting constructive feedback
* Accepting responsibility and apologizing to those affected by our mistakes,
and learning from the experience
* Focusing on what is best not just for us as individuals, but for the overall
community

Examples of unacceptable behavior include:

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

## Enforcement Responsibilities

Community leaders are responsible for clarifying and enforcing our standards of
acceptable behavior and will take appropriate and fair corrective action in
response to any behavior that they deem inappropriate, threatening, offensive,
or harmful.

Community leaders 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, and will communicate reasons for moderation
decisions when appropriate.

## Scope

This Code of Conduct applies within all community spaces, and also applies when
an individual is officially representing the community in public spaces.
Examples of representing our community include using an official email address,
posting via an official social media account, or acting as an appointed
representative at an online or offline event.

## Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be
reported to the community leaders responsible for enforcement at
[INSERT CONTACT METHOD].
All complaints will be reviewed and investigated promptly and fairly.

All community leaders are obligated to respect the privacy and security of the
reporter of any incident.

## Enforcement Guidelines

Community leaders will follow these Community Impact Guidelines in determining
the consequences for any action they deem in violation of this Code of Conduct:

### 1. Correction

**Community Impact**: Use of inappropriate language or other behavior deemed
unprofessional or unwelcome in the community.

**Consequence**: A private, written warning from community leaders, providing
clarity around the nature of the violation and an explanation of why the
behavior was inappropriate. A public apology may be requested.

### 2. Warning

**Community Impact**: A violation through a single incident or series of
actions.

**Consequence**: A warning with consequences for continued behavior. No
interaction with the people involved, including unsolicited interaction with
those enforcing the Code of Conduct, for a specified period of time. This
includes avoiding interactions in community spaces as well as external channels
like social media. Violating these terms may lead to a temporary or permanent
ban.

### 3. Temporary Ban

**Community Impact**: A serious violation of community standards, including
sustained inappropriate behavior.

**Consequence**: A temporary ban from any sort of interaction or public
communication with the community for a specified period of time. No public or
private interaction with the people involved, including unsolicited interaction
with those enforcing the Code of Conduct, is allowed during this period.
Violating these terms may lead to a permanent ban.

### 4. Permanent Ban

**Community Impact**: Demonstrating a pattern of violation of community
standards, including sustained inappropriate behavior, harassment of an
individual, or aggression toward or disparagement of classes of individuals.

**Consequence**: A permanent ban from any sort of public interaction within the
community.

## Attribution

This Code of Conduct is adapted from the [Contributor Covenant][homepage],
version 2.1, available at
[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].

Community Impact Guidelines were inspired by
[Mozilla's code of conduct enforcement ladder][Mozilla CoC].

For answers to common questions about this code of conduct, see the FAQ at
[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
[https://www.contributor-covenant.org/translations][translations].

[homepage]: https://www.contributor-covenant.org
[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
[Mozilla CoC]: https://github.com/mozilla/diversity
[FAQ]: https://www.contributor-covenant.org/faq
[translations]: https://www.contributor-covenant.org/translations

61 changes: 61 additions & 0 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,61 @@
<!--
!! THIS FILE WAS GENERATED USING repoman !!
Modify `repo.yaml` instead and use `repoman` to update this file
See: https://github.com/metaborg/metaborg-gradle/
-->

# MB Rep

## How to Contribute
Thank you for wanting to contribute to this project! :tada::+1:

> **Note**:
> We may not deal with your issue or pull request in a timely manner, or at all.
> We also reserve the right to change your contribution in any way we deem fit
> for this project, or even outright reject it.
#### **You have a question?**
Search the [Discussions][1] and [Stackoverflow][3] to see whether your question
has already been answered, or ask your question there.
Please do **not** make an issue on the Github repository.


#### **You found a bug**
Search the [Issues][2] to ensure the bug has not been reported before.

If the bug is new, open a new issue with a _clear title and description_.
Please indicate:
- what you did,
- what you expected to happen, and
- what actually happened.

Try to include as much relevant information as you have.
For example, a code sample or executable test case are very helpful.


#### **You wrote a patch with a cosmetic change**
Please do not submit pull requests for cosmetic changes,
such as whitespace and formatting changes.
We will reject them.


#### **You wrote a patch with a bug fix**
Thank you! Please open a GitHub pull request with the patch.


#### **You wrote a patch that adds a new feature or changes an existing one**
Please open an issue _first_, so we can discuss the change.


#### **You want to contribute to the documentation or test suite**
Thank you! Please open a GitHub pull request with the patch.

---

Thanks! :heart: :heart: :heart:

[Programming Languages Group](https://pl.ewi.tudelft.nl/), [Delft University of Technology](https://www.tudelft.nl/)

[1]: https://github.com/metaborg/mb-rep/discussions
[2]: https://github.com/metaborg/mb-rep/issues
[3]: https://stackoverflow.com/
Loading

0 comments on commit f020bab

Please sign in to comment.