Skip to content

Commit d904431

Browse files
AhmarZaidiup1512001aviral-mittaldanish17AnuragVasanwala
committed
chore: initial commit
Migrated code from private repository Prepares for first public release Preserves original functionality and history Co-authored-by: Ahmar Zaidi <ahmarzaidi07@gmail.com> Co-authored-by: Utsav Patel <75293077+up1512001@users.noreply.github.com> Co-authored-by: Aviral Mittal <aviral.ideabox@gmail.com> Co-authored-by: Danish Shakeel <danishshakeel54@gmail.com> Co-authored-by: Anurag Vasanwala <AnuragVasanwala@gmail.com> Co-authored-by: Vishal Kotak <vishalkotak200@gmail.com> Co-authored-by: Rishav Dutta <duttarishav2510@gmail.com> Co-authored-by: Sushant Kakade <sushantkakade13@gmail.com>
0 parents  commit d904431

Some content is hidden

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

80 files changed

+39296
-0
lines changed

‎.browserslistrc‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
extends @wordpress/browserslist-config

‎.changeset/README.md‎

Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,31 @@
1+
# Changesets
2+
3+
This project uses [Changesets](https://github.com/changesets/changesets) for versioning and generating changelogs in the repo.
4+
5+
To generate a Changeset (_copied and modified from [Changesets' docs](https://github.com/changesets/changesets/blob/01c037c0462540196b5d3d0c0241d8752b465b4b/docs/adding-a-changeset.md)_):
6+
7+
1. Run `npm run changeset` in the root of the OneMedia repo.
8+
2. You will be prompted to select a bump type. Select a **Major**, **Minor**, or **Patch** bump.
9+
10+
- **Major**: Any form of breaking change.
11+
- **Minor**: New (non-breaking) features or changes.
12+
- **Patch**: Bug fixes.
13+
14+
3. Your final prompt will be to provide a message to go along with the changeset. This message will be written to the changeset when the next release is made.
15+
16+
> ⚠️ **Important**
17+
>
18+
> Remember to follow [Conventional Commits formatting](https://www.conventionalcommits.org/en/v1.0.0/) and to use imperative language in your changeset message.
19+
>
20+
> For example, "feat: Add new feature" instead of "Added new feature".
21+
22+
After this, a new changeset will be added which is a markdown file with YAML front matter.
23+
24+
```bash
25+
-| .changeset/
26+
-|-| UNIQUE_ID.md
27+
```
28+
29+
The message you typed can be found in the markdown file. If you want to expand on it, you can write as much markdown as you want, which will all be added to the changelog on publish. You can also rename the markdown file with a more suitable name if needed.
30+
31+
4. Once you are happy with the changeset, commit the file to your branch.

‎.changeset/config.json‎

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
{
2+
"$schema": "https://unpkg.com/@changesets/config@3.1.1/schema.json",
3+
"changelog": "@changesets/cli/changelog",
4+
"commit": false,
5+
"fixed": [],
6+
"linked": [],
7+
"access": "restricted",
8+
"baseBranch": "main",
9+
"updateInternalDependencies": "patch",
10+
"ignore": []
11+
}

‎.editorconfig‎

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
# WordPress Coding Standards.
2+
# https://make.wordpress.org/core/handbook/coding-standards/
3+
4+
root = true
5+
6+
[*]
7+
charset = utf-8
8+
end_of_line = lf
9+
insert_final_newline = true
10+
trim_trailing_whitespace = true
11+
indent_style = tab
12+
13+
[{.babelrc,.eslintrc,.rtlcssrc,*.json,*.yml}]
14+
indent_style = space
15+
indent_size = 2
16+
17+
[*.md]
18+
trim_trailing_whitespace = false

‎.eslintignore‎

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,4 @@
1+
**/*.min.js
2+
**/node_modules/**
3+
**/vendor/**
4+
build/*

‎.eslintrc‎

Lines changed: 38 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
1+
{
2+
"root": true,
3+
"extends": [
4+
"plugin:@wordpress/eslint-plugin/recommended-with-formatting",
5+
"plugin:import/recommended",
6+
"plugin:eslint-comments/recommended"
7+
],
8+
"plugins": [],
9+
"env": {
10+
"browser": true
11+
},
12+
"globals": {
13+
"_": true,
14+
"oneMediaSettings": true,
15+
"oneMediaSetupSettings": true,
16+
"oneMediaMediaSharing": true,
17+
"oneMediaMediaUpload": true,
18+
"oneMediaMediaFrame": true
19+
},
20+
"rules": {
21+
"jsdoc/check-indentation": "error",
22+
"no-shadow": "warn"
23+
},
24+
"overrides": [
25+
{
26+
"files": [
27+
"**/__tests__/**/*.js",
28+
"**/test/*.js",
29+
"**/?(*.)test.js",
30+
"tests/js/**/*.js"
31+
],
32+
"extends": ["plugin:jest/all"],
33+
"rules": {
34+
// Add Rules for Jest here.
35+
}
36+
}
37+
]
38+
}

‎.github/ISSUE_TEMPLATE/bug_report.md‎

Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,31 @@
1+
---
2+
name: "Bug Report"
3+
about: "If something isn't working as expected"
4+
title: ''
5+
labels: ''
6+
assignees: ''
7+
---
8+
9+
## Bug Report
10+
11+
**Current Behavior**
12+
A clear and concise description of the buggy behavior.
13+
14+
**Expected behavior/code**
15+
A clear and concise description of what you expected to happen (or code).
16+
17+
**Steps to reproduce the bug**
18+
Steps to reproduce if any.
19+
20+
**Testing Environment (if applicable)**
21+
22+
- Browser used
23+
- OS: [e.g. OSX 10.15.x, Ubuntu 18.04]
24+
- Plugins used
25+
- ...
26+
27+
**Possible Solution**
28+
<!--- Only if you have suggestions on a fix for the bug -->
29+
30+
**Additional context/Screenshots**
31+
Add any other context about the problem here. If applicable, add screenshots to help explain.

‎.github/ISSUE_TEMPLATE/feature_request.md‎

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
---
2+
name: "Feature Request"
3+
about: "Suggest an idea for this project."
4+
title: ''
5+
labels: ''
6+
assignees: ''
7+
---
8+
9+
## Feature Request
10+
11+
**Is your feature request related to a problem? Please describe.**
12+
A clear and concise description of what the problem is. Ex. I have an issue when [...]
13+
14+
**Describe the solution you'd like**
15+
A clear and concise description of what you want to happen. Add any considered drawbacks.
16+
17+
**Describe alternatives you've considered**
18+
A clear and concise description of any alternative solutions or features you've considered.
19+
20+
**Documentation, Adoption, Migration Strategy (if applicable)**
21+
If you can, explain how users will be able to use this and possibly write out a version of the docs.
22+
Maybe a screenshot or design?

‎.github/PULL_REQUEST_TEMPLATE.md‎

Lines changed: 45 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,45 @@
1+
<!--
2+
Thanks for taking the time to submit a Pull Request.
3+
Please make sure to review the [Development Guidelines](../docs/DEVELOPMENT.md) before submitting your PR.
4+
-->
5+
6+
## What
7+
<!-- In a few words, what does this PR actually change -->
8+
9+
## Why
10+
<!-- Why is this PR necessary? Please any existing previous issue(s) or PR(s) and include a short summary here, too. -->
11+
12+
### Related Issue(s):
13+
<!-- E.g.
14+
- Fixes | Closes | Part of: #123
15+
-->
16+
17+
## How
18+
<!-- How does your PR address the issue at hand? What are the implementation details? Please be specific. -->
19+
20+
## Testing Instructions
21+
<!-- Please include step by step instructions on how to test this PR. -->
22+
<!-- 1. Open a Post or Page. -->
23+
<!-- 2. Insert a Heading Block. -->
24+
<!-- 3. etc. -->
25+
26+
## Screenshots
27+
<!-- Include relevant screenshots proving the PR works as intended. -->
28+
29+
## Additional Info
30+
<!-- Please include any relevant logs, error output, etc -->
31+
32+
## Checklist
33+
<!--
34+
We encourage you to complete this checklist to the best of your abilities.
35+
If you can't do everything, that's okay too.
36+
[Development Guidelines](../docs/DEVELOPMENT.md)
37+
-->
38+
39+
- [ ] I have read the [Contribution Guidelines](https://github.com/rtCamp/OneMedia/blob/main/docs/CONTRIBUTING.md).
40+
- [ ] I have read the [Development Guidelines](https://github.com/rtCamp/OneMedia/blob/main/docs/DEVELOPMENT.md).
41+
- [ ] My code is tested to the best of my abilities.
42+
- [ ] My code passes all lints (ESLint etc.).
43+
- [ ] My code has detailed inline documentation.
44+
- [ ] I have updated the project documentation as needed.
45+
- [ ] I have added a changeset for this PR using `npm run changeset`.

‎.github/workflows/phpcs_on_pull_request.yml‎

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
name: Inspections
2+
on: pull_request
3+
4+
jobs:
5+
runPHPCSInspection:
6+
name: Run PHPCS inspection
7+
runs-on: ubuntu-latest
8+
9+
steps:
10+
- uses: actions/checkout@v4
11+
with:
12+
ref: ${{ github.event.pull_request.head.sha }}
13+
14+
- name: Run PHPCS inspection
15+
uses: rtCamp/action-phpcs-code-review@master
16+
env:
17+
SKIP_FOLDERS: "tests,.github,languages,assets,bin,actions,docs"
18+
GH_BOT_TOKEN: ${{ secrets.RTBOT_TOKEN }}
19+
PHPCS_SNIFFS_EXCLUDE: "WordPress.Files.FileName"
20+
with:
21+
args: WordPress,WordPress-Core,WordPress-Docs

0 commit comments

Comments
 (0)