Skip to content

Commit ab1c38d

Browse files
committed
Initial commit
0 parents  commit ab1c38d

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

45 files changed

+2036
-0
lines changed

.circleci/config.pkl

Lines changed: 40 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,40 @@
1+
//===----------------------------------------------------------------------===//
2+
// Copyright © 2024 Apple Inc. and the Pkl project authors. All rights reserved.
3+
//
4+
// Licensed under the Apache License, Version 2.0 (the "License");
5+
// you may not use this file except in compliance with the License.
6+
// You may obtain a copy of the License at
7+
//
8+
// https://www.apache.org/licenses/LICENSE-2.0
9+
//
10+
// Unless required by applicable law or agreed to in writing, software
11+
// distributed under the License is distributed on an "AS IS" BASIS,
12+
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
13+
// See the License for the specific language governing permissions and
14+
// limitations under the License.
15+
//===----------------------------------------------------------------------===//
16+
amends "package://pkg.pkl-lang.org/pkl-project-commons/pkl.impl.circleci@1.0.0#/PklCI.pkl"
17+
18+
jobs {
19+
["build"] {
20+
docker {
21+
new {
22+
image = "cimg/openjdk:17.0"
23+
}
24+
}
25+
steps {
26+
"checkout"
27+
new RunStep { command = "./gradlew build" }
28+
}
29+
}
30+
}
31+
32+
local buildWorkflow: Workflow = new {
33+
jobs {
34+
"build"
35+
}
36+
}
37+
38+
prb = buildWorkflow
39+
40+
main = buildWorkflow

.circleci/config.yml

Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
# Generated from CircleCI.pkl. DO NOT EDIT.
2+
version: '2.1'
3+
orbs:
4+
pr-approval: apple/pr-approval@0.1.0
5+
jobs:
6+
build:
7+
steps:
8+
- checkout
9+
- run:
10+
command: ./gradlew build
11+
docker:
12+
- image: cimg/openjdk:17.0
13+
workflows:
14+
prb:
15+
jobs:
16+
- hold:
17+
type: approval
18+
- pr-approval/authenticate:
19+
context: pkl-pr-approval
20+
- build:
21+
requires:
22+
- hold
23+
- pr-approval/authenticate
24+
when:
25+
matches:
26+
value: << pipeline.git.branch >>
27+
pattern: ^pull/\d+(/head)?$
28+
main:
29+
jobs:
30+
- build
31+
when:
32+
equal:
33+
- main
34+
- << pipeline.git.branch >>

.gitattributes

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
*.pkl linguist-language=Groovy

.gitignore

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
# Mac
2+
.DS_STORE
3+
4+
# Gradle
5+
.gradle/
6+
build/
7+
generated/
8+
9+
# IntelliJ
10+
out/
11+
.idea/
12+
*.iml
13+
*.ipr
14+
*.iws

CODE_OF_CONDUCT.adoc

Lines changed: 78 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,78 @@
1+
== Code of Conduct
2+
3+
=== Our Pledge
4+
5+
In the interest of fostering an open and welcoming environment, we as
6+
contributors and maintainers pledge to making participation in our
7+
project and our community a harassment-free experience for everyone,
8+
regardless of age, body size, disability, ethnicity, sex
9+
characteristics, gender identity and expression, level of experience,
10+
education, socio-economic status, nationality, personal appearance,
11+
race, religion, or sexual identity and orientation.
12+
13+
=== Our Standards
14+
15+
Examples of behavior that contributes to creating a positive environment
16+
include:
17+
18+
* Using welcoming and inclusive language
19+
* Being respectful of differing viewpoints and experiences
20+
* Gracefully accepting constructive criticism
21+
* Focusing on what is best for the community
22+
* Showing empathy towards other community members
23+
24+
Examples of unacceptable behavior by participants include:
25+
26+
* The use of sexualized language or imagery and unwelcome sexual
27+
attention or advances
28+
* Trolling, insulting/derogatory comments, and personal or political
29+
attacks
30+
* Public or private harassment
31+
* Publishing others’ private information, such as a physical or
32+
electronic address, without explicit permission
33+
* Other conduct which could reasonably be considered inappropriate in a
34+
professional setting
35+
36+
=== Our Responsibilities
37+
38+
Project maintainers are responsible for clarifying the standards of
39+
acceptable behavior and are expected to take appropriate and fair
40+
corrective action in response to any instances of unacceptable behavior.
41+
42+
Project maintainers have the right and responsibility to remove, edit,
43+
or reject comments, commits, code, wiki edits, issues, and other
44+
contributions that are not aligned to this Code of Conduct, or to ban
45+
temporarily or permanently any contributor for other behaviors that they
46+
deem inappropriate, threatening, offensive, or harmful.
47+
48+
=== Scope
49+
50+
This Code of Conduct applies within all project spaces, and it also
51+
applies when an individual is representing the project or its community
52+
in public spaces. Examples of representing a project or community
53+
include using an official project e-mail address, posting via an
54+
official social media account, or acting as an appointed representative
55+
at an online or offline event. Representation of a project may be
56+
further defined and clarified by project maintainers.
57+
58+
=== Enforcement
59+
60+
Instances of abusive, harassing, or otherwise unacceptable behavior may
61+
be reported by contacting the open source team at
62+
opensource-conduct@group.apple.com. All complaints will be reviewed and
63+
investigated and will result in a response that is deemed necessary and
64+
appropriate to the circumstances. The project team is obligated to
65+
maintain confidentiality with regard to the reporter of an incident.
66+
Further details of specific enforcement policies may be posted
67+
separately.
68+
69+
Project maintainers who do not follow or enforce the Code of Conduct in
70+
good faith may face temporary or permanent repercussions as determined
71+
by other members of the project’s leadership.
72+
73+
=== Attribution
74+
75+
This Code of Conduct is adapted from the
76+
https://www.contributor-covenant.org[Contributor Covenant], version 1.4,
77+
available at
78+
https://www.contributor-covenant.org/version/1/4/code-of-conduct.html

CONTRIBUTING.adoc

Lines changed: 43 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,43 @@
1+
:uri-github-issue-pkl-jvm-examples: https://github.com/apple/pkl-jvm-examples/issues/new
2+
:uri-seven-rules: https://cbea.ms/git-commit/#seven-rules
3+
4+
= Pkl JVM Examples Contributors Guide
5+
6+
Welcome to the Pkl community, and thank you for contributing!
7+
This guide explains how to get involved.
8+
9+
* <<Licensing>>
10+
* <<Issue Tracking>>
11+
* <<Pull Requests>>
12+
13+
== Licensing
14+
15+
Pkl JVM Examples is released under the Apache 2.0 license.
16+
This is why we require that, by submitting a pull request, you acknowledge that you have the right to license your contribution to Apple and the community, and agree that your contribution is licensed under the Apache 2.0 license.
17+
18+
== Issue Tracking
19+
20+
To file a bug or feature request, use {uri-github-issue-pkl-jvm-examples}[GitHub].
21+
Be sure to include the following information:
22+
23+
* Context
24+
** What are/were you trying to achieve?
25+
** What's the impact of this bug/feature?
26+
27+
== Pull Requests
28+
29+
When preparing a pull request, follow this checklist:
30+
31+
* Imitate the conventions of surrounding code.
32+
* Follow the {uri-seven-rules}[seven rules] of great Git commit messages:
33+
** Separate subject from body with a blank line.
34+
** Limit the subject line to 50 characters.
35+
** Capitalize the subject line.
36+
** Do not end the subject line with a period.
37+
** Use the imperative mood in the subject line.
38+
** Wrap the body at 72 characters.
39+
** Use the body to explain what and why vs. how.
40+
41+
== Maintainers
42+
43+
The project’s maintainers (those with write access to the upstream repository) are listed in link:MAINTAINERS.adoc[].

0 commit comments

Comments
 (0)