Skip to content

Commit 61baa80

Browse files
amirisbackamirisback
authored
Initial commit
0 parents  commit 61baa80

File tree

132 files changed

+5657
-0
lines changed

Some content is hidden

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

132 files changed

+5657
-0
lines changed

‎.github/FUNDING.yml‎

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
# These are supported funding model platforms
2+
3+
github: # Replace with up to 4 GitHub Sponsors-enabled usernames e.g., [user1, user2]
4+
patreon: # Replace with a single Patreon username
5+
open_collective: # Replace with a single Open Collective username
6+
ko_fi: # Replace with a single Ko-fi username
7+
tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
8+
community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry
9+
liberapay: # Replace with a single Liberapay username
10+
issuehunt: # Replace with a single IssueHunt username
11+
otechie: # Replace with a single Otechie username
12+
custom: https://saweria.co/amirisback

‎.github/workflows/android-ci.yml‎

Lines changed: 62 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,62 @@
1+
name: Android CI
2+
3+
env:
4+
# The name of the main module repository
5+
main_project_module: app
6+
7+
# The name of the Play Store
8+
playstore_name: Frogobox ID
9+
10+
on:
11+
# Triggers the workflow on push or pull request events but only for default and protected branches
12+
push:
13+
branches: [ master ]
14+
pull_request:
15+
branches: [ master ]
16+
17+
workflow_dispatch:
18+
19+
jobs:
20+
build:
21+
22+
runs-on: ubuntu-latest
23+
24+
steps:
25+
- uses: actions/checkout@v1
26+
27+
# Set Current Date As Env Variable
28+
- name: Set current date as env variable
29+
run: echo "date_today=$(date +'%Y-%m-%d')" >> $GITHUB_ENV
30+
31+
# Set Repository Name As Env Variable
32+
- name: Set repository name as env variable
33+
run: echo "repository_name=$(echo '${{ github.repository }}' | awk -F '/' '{print $2}')" >> $GITHUB_ENV
34+
35+
- name: Set Up JDK
36+
uses: actions/setup-java@v1
37+
with:
38+
java-version: 11
39+
40+
- name: Change wrapper permissions
41+
run: chmod +x ./gradlew
42+
43+
# Run Tests Build
44+
- name: Run gradle tests
45+
run: ./gradlew test
46+
47+
# Run Build Project
48+
- name: Build gradle project
49+
run: ./gradlew build
50+
51+
# Create Bundle AAB Release
52+
# Noted for main module build [main_project_module]:bundleRelease
53+
- name: Build app bundle release (AAB) - ${{ env.main_project_module }} module
54+
run: ./gradlew ${{ env.main_project_module }}:bundleRelease
55+
56+
# Upload Artifact Build
57+
# Noted For Output [main_project_module]/build/outputs/bundle/release/
58+
- name: Upload AAB (App Bundle) Release - ${{ env.repository_name }}
59+
uses: actions/upload-artifact@v2
60+
with:
61+
name: ${{ env.date_today }} - ${{ env.playstore_name }} - ${{ env.repository_name }} - App bundle(s) AAB release generated
62+
path: ${{ env.main_project_module }}/build/outputs/bundle/release/

‎.github/workflows/detekt-analysis.yml‎

Lines changed: 103 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,103 @@
1+
# This workflow performs a static analysis of your Kotlin source code using
2+
# Detekt.
3+
#
4+
# Scans are triggered:
5+
# 1. On every push to default and protected branches
6+
# 2. On every Pull Request targeting the default branch
7+
# 3. On a weekly schedule
8+
# 4. Manually, on demand, via the "workflow_dispatch" event
9+
#
10+
# The workflow should work with no modifications, but you might like to use a
11+
# later version of the Detekt CLI by modifing the $DETEKT_RELEASE_TAG
12+
# environment variable.
13+
name: Scan with Detekt
14+
15+
on:
16+
# Triggers the workflow on push or pull request events but only for default and protected branches
17+
push:
18+
branches: [ master ]
19+
pull_request:
20+
branches: [ master ]
21+
schedule:
22+
- cron: '27 4 * * 1'
23+
24+
# Allows you to run this workflow manually from the Actions tab
25+
workflow_dispatch:
26+
27+
env:
28+
# Release tag associated with version of Detekt to be installed
29+
# SARIF support (required for this workflow) was introduced in Detekt v1.15.0
30+
DETEKT_RELEASE_TAG: v1.15.0
31+
32+
# A workflow run is made up of one or more jobs that can run sequentially or in parallel
33+
jobs:
34+
# This workflow contains a single job called "scan"
35+
scan:
36+
name: Scan
37+
# The type of runner that the job will run on
38+
runs-on: ubuntu-latest
39+
40+
# Steps represent a sequence of tasks that will be executed as part of the job
41+
steps:
42+
# Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
43+
- uses: actions/checkout@v2
44+
45+
# Gets the download URL associated with the $DETEKT_RELEASE_TAG
46+
- name: Get Detekt download URL
47+
id: detekt_info
48+
env:
49+
GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
50+
run: |
51+
DETEKT_DOWNLOAD_URL=$( gh api graphql --field tagName=$DETEKT_RELEASE_TAG --raw-field query='
52+
query getReleaseAssetDownloadUrl($tagName: String!) {
53+
repository(name: "detekt", owner: "detekt") {
54+
release(tagName: $tagName) {
55+
releaseAssets(name: "detekt", first: 1) {
56+
nodes {
57+
downloadUrl
58+
}
59+
}
60+
}
61+
}
62+
}
63+
' | \
64+
jq --raw-output '.data.repository.release.releaseAssets.nodes[0].downloadUrl' )
65+
echo "::set-output name=download_url::$DETEKT_DOWNLOAD_URL"
66+
67+
# Sets up the detekt cli
68+
- name: Setup Detekt
69+
run: |
70+
dest=$( mktemp -d )
71+
curl --request GET \
72+
--url ${{ steps.detekt_info.outputs.download_url }} \
73+
--silent \
74+
--location \
75+
--output $dest/detekt
76+
chmod a+x $dest/detekt
77+
echo $dest >> $GITHUB_PATH
78+
79+
# Performs static analysis using Detekt
80+
- name: Run Detekt
81+
continue-on-error: true
82+
run: |
83+
detekt --input ${{ github.workspace }} --report sarif:${{ github.workspace }}/detekt.sarif.json
84+
85+
# Modifies the SARIF output produced by Detekt so that absolute URIs are relative
86+
# This is so we can easily map results onto their source files
87+
# This can be removed once relative URI support lands in Detekt: https://git.io/JLBbA
88+
- name: Make artifact location URIs relative
89+
continue-on-error: true
90+
run: |
91+
echo "$(
92+
jq \
93+
--arg github_workspace ${{ github.workspace }} \
94+
'. | ( .runs[].results[].locations[].physicalLocation.artifactLocation.uri |= if test($github_workspace) then .[($github_workspace | length | . + 1):] else . end )' \
95+
${{ github.workspace }}/detekt.sarif.json
96+
)" > ${{ github.workspace }}/detekt.sarif.json
97+
98+
# Uploads results to GitHub repository using the upload-sarif action
99+
- uses: github/codeql-action/upload-sarif@v1
100+
with:
101+
# Path to SARIF file relative to the root of the repository
102+
sarif_file: ${{ github.workspace }}/detekt.sarif.json
103+
checkout_path: ${{ github.workspace }}

‎.gitignore‎

Lines changed: 35 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
*.iml
2+
/.gradle
3+
.gradle
4+
.idea
5+
/local.properties
6+
/.idea/libraries
7+
/.idea/modules.xml
8+
/.idea/workspace.xml
9+
.DS_Store
10+
build
11+
/build
12+
/captures
13+
.externalNativeBuild
14+
15+
built application files
16+
.apk
17+
.ap_
18+
19+
files for the dex VM
20+
*.dex
21+
22+
Java class files
23+
*.class
24+
25+
generated files
26+
bin/
27+
gen/
28+
.externalNativeBuild/
29+
30+
Local configuration file (sdk path, etc)
31+
local.properties
32+
app/version.properties
33+
34+
# SonarQube
35+
.sonar/

‎CODE_OF_CONDUCT.md‎

Lines changed: 46 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,46 @@
1+
# Contributor Covenant Code of Conduct
2+
3+
## Our Pledge
4+
5+
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.
6+
7+
## Our Standards
8+
9+
Examples of behavior that contributes to creating a positive environment include:
10+
11+
* Using welcoming and inclusive language
12+
* Being respectful of differing viewpoints and experiences
13+
* Gracefully accepting constructive criticism
14+
* Focusing on what is best for the community
15+
* Showing empathy towards other community members
16+
17+
Examples of unacceptable behavior by participants include:
18+
19+
* The use of sexualized language or imagery and unwelcome sexual attention or advances
20+
* Trolling, insulting/derogatory comments, and personal or political attacks
21+
* Public or private harassment
22+
* Publishing others' private information, such as a physical or electronic address, without explicit permission
23+
* Other conduct which could reasonably be considered inappropriate in a professional setting
24+
25+
## Our Responsibilities
26+
27+
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.
28+
29+
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.
30+
31+
## Scope
32+
33+
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.
34+
35+
## Enforcement
36+
37+
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at faisalamircs@gmail.com. The project team will review and investigate all complaints, and will respond in a way that it deems 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.
38+
39+
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.
40+
41+
## Attribution
42+
43+
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
44+
45+
[homepage]: http://contributor-covenant.org
46+
[version]: http://contributor-covenant.org/version/1/4/

0 commit comments

Comments
 (0)