Skip to content

Commit c4dbf8e

Browse files
committed
erpnext: track bundled hrms source in src/hrms
1 parent 2c14206 commit c4dbf8e

1,530 files changed

Lines changed: 526858 additions & 3 deletions

File tree

Some content is hidden

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

.gitignore

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,4 @@ mk.sh
88
.claude
99
_bmad-output
1010

11-
# Pre-downloaded app sources (large, user-managed, not version-controlled)
12-
apps/erpnext/src/hrms/*
13-
!apps/erpnext/src/hrms/.gitkeep
11+
# Pre-downloaded app sources
Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
# Root editor config file
2+
root = true
3+
4+
# Common settings
5+
[*]
6+
end_of_line = lf
7+
insert_final_newline = true
8+
trim_trailing_whitespace = true
9+
charset = utf-8
10+
11+
# js indentation settings
12+
[{*.js,*.ts,*.vue,*.css,*.scss,*.html}]
13+
indent_style = tab
14+
indent_size = 4
15+
max_line_length = 99
Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,30 @@
1+
# Since version 2.23 (released in August 2019), git-blame has a feature
2+
# to ignore or bypass certain commits.
3+
#
4+
# This file contains a list of commits that are not likely what you
5+
# are looking for in a blame, such as mass reformatting or renaming.
6+
# You can set this file as a default ignore file for blame by running
7+
# the following command.
8+
#
9+
# $ git config blame.ignoreRevsFile .git-blame-ignore-revs
10+
11+
# sort and cleanup imports
12+
4872c156974291f0c4c88f26033fef0b900ca995
13+
14+
# old black formatting commit (from erpnext)
15+
76c895a6c659356151433715a1efe9337e348c11
16+
17+
# bulk formatting
18+
b55d6e27af6bd274dfa47e66a3012ddec68ce798
19+
20+
# bulk formatting PWA frontend code
21+
f37f15b2b5329e3b0b35891e1c4fd82f48562c6d
22+
23+
# bulk formatting PWA frontend code
24+
920daa1a3ddccaefaf7b9348f850831d6e0a0e6b
25+
26+
# python ruff formatting
27+
b68457552bb3540565267f23fbfcee35c9f86e1c
28+
29+
# js, scss prettier formatting
30+
1ab1d6238171a5cee3263812402a8b82e7131cb1
Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
# This is a comment.
2+
# Each line is a file pattern followed by one or more owners.
3+
4+
# These owners will be the default owners for everything in
5+
# the repo. Unless a later match takes precedence.
6+
7+
hrms/hr/ @ruchamahabal @asmitahase
8+
hrms/payroll/ @ruchamahabal @AyshaHakeem @iamraheelkhan
9+
10+
frontend/ @ruchamahabal @asmitahase
11+
roster/ @ruchamahabal @asmitahase
12+
13+
.github/ @asmitahase
Lines changed: 81 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,81 @@
1+
---
2+
name: Bug Report
3+
description: Report a bug encountered while using Frappe HR
4+
labels: ["bug"]
5+
6+
body:
7+
- type: markdown
8+
attributes:
9+
value: |
10+
Welcome to Frappe HR issue tracker! Before creating an issue, please consider the following:
11+
12+
1. This tracker should only be used to report bugs and request features / enhancements to Frappe HR
13+
- For questions and general support, checkout the [documentation](https://frappehr.com/docs) or use the [forum](https://discuss.frappe.io) to get inputs from the open source community.
14+
- For documentation issues, propose edit on the [documentation site](https://frappehr.com/docs) directly.
15+
2. When making a bug report, make sure you provide all required information. The easier it is for
16+
maintainers to reproduce, the faster it'll be fixed.
17+
3. If you think you know what the reason for the bug is, share it with us. Maybe put in a PR 😉
18+
19+
- type: textarea
20+
id: bug-info
21+
attributes:
22+
label: Information about bug
23+
description: Also tell us, what did you expect to happen? If applicable, add screenshots to help explain your problem.
24+
placeholder: Please provide as much information as possible.
25+
validations:
26+
required: true
27+
28+
- type: dropdown
29+
id: module
30+
attributes:
31+
label: Module
32+
description: Select the affected module of Frappe HR.
33+
multiple: true
34+
options:
35+
- HR
36+
- Payroll
37+
- other
38+
validations:
39+
required: true
40+
41+
- type: textarea
42+
id: exact-version
43+
attributes:
44+
label: Version
45+
description: Share exact version number of Frappe, ERPNext and Frappe HR you are using.
46+
placeholder: |
47+
Frappe version -
48+
ERPNext version -
49+
Frappe HR version -
50+
validations:
51+
required: true
52+
53+
- type: dropdown
54+
id: install-method
55+
attributes:
56+
label: Installation method
57+
options:
58+
- docker
59+
- easy-install
60+
- manual install
61+
- FrappeCloud
62+
validations:
63+
required: false
64+
65+
- type: textarea
66+
id: logs
67+
attributes:
68+
label: Relevant log output / Stack trace / Full Error Message.
69+
description: Please copy and paste any relevant log output. This will be automatically formatted.
70+
render: shell
71+
72+
- type: checkboxes
73+
id: terms
74+
attributes:
75+
label: Code of Conduct
76+
description: |
77+
By submitting this issue, you agree to follow our [Code of Conduct](https://github.com/frappe/hrms/blob/develop/CODE_OF_CONDUCT.md)
78+
options:
79+
- label: I agree to follow this project's Code of Conduct
80+
required: true
81+
...
Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
blank_issues_enabled: false
2+
contact_links:
3+
- name: Community Forum
4+
url: https://discuss.frappe.io/
5+
about: For general QnA, discussions and community help.
Lines changed: 50 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,50 @@
1+
---
2+
name: Feature Request
3+
description: Suggest an idea to improve Frappe HR
4+
labels: ["feature-request"]
5+
6+
body:
7+
- type: markdown
8+
attributes:
9+
value: |
10+
Welcome to Frappe HR issue tracker! Before submitting a request, please consider the following:
11+
12+
1. This tracker should only be used to report bugs and request features / enhancements to Frappe HR
13+
- For questions and general support, checkout the [documentation](https://docs.frappe.io/hr) or use the [forum](https://discuss.frappe.io) to get inputs from the open source community.
14+
2. Use the search function before creating a new issue. Duplicates will be closed and directed to
15+
the original discussion.
16+
3. When making a feature request, make sure to be as verbose as possible. The better you convey your message, the greater the drive to make it happen.
17+
18+
19+
Please keep in mind that we get many many requests and we can't possibly work on all of them, we prioritize development based on the goals of the product and organization. Feature requests are still welcome as it helps us in research when we do decide to work on the requested feature.
20+
21+
If you're in urgent need to a feature, please try the following channels to get paid developments done quickly:
22+
1. Certified Frappe partners: https://frappe.io/partners
23+
2. Developer community on Frappe forums: https://discuss.frappe.io/c/developers/5
24+
3. Telegram group for Frappe HR development work: https://t.me/frappehr
25+
26+
- type: textarea
27+
id: problem-info
28+
attributes:
29+
label: Is your feature request related to a problem? Please describe.
30+
description: A clear and concise description of what the problem is. Eg. I'm always frustrated when [...]
31+
placeholder: Please provide as much information as possible.
32+
33+
- type: textarea
34+
id: solution-info
35+
attributes:
36+
label: Describe the solution you'd like
37+
description: A clear and concise description of what you want to happen.
38+
39+
- type: textarea
40+
id: alternatives-info
41+
attributes:
42+
label: Describe the alternatives you've considered
43+
description: A clear and concise description of any alternative solutions or features you've considered.
44+
45+
- type: textarea
46+
id: additional-info
47+
attributes:
48+
label: Additional context
49+
description: Add any other context or screenshots about the feature request here.
50+
...
Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
<!--
2+
3+
Some key notes before you open a PR:
4+
5+
1. Select which branch should this PR be merged in?
6+
2. PR name follows [convention](http://karma-runner.github.io/4.0/dev/git-commit-msg.html)
7+
3. All tests pass locally, UI and Unit tests
8+
4. All business logic and validations must be on the server-side
9+
5. Update necessary Documentation
10+
6. Put `closes #XXXX` in your comment to auto-close the issue that your PR fixes
11+
12+
13+
Also, if you're new here
14+
15+
- Documentation Guidelines => https://github.com/frappe/erpnext/wiki/Page-format-for-ERPNext-docs
16+
17+
- Contribution Guide => https://github.com/frappe/erpnext/wiki/Contribution-Guidelines
18+
19+
- Pull Request Checklist => https://github.com/frappe/erpnext/wiki/Pull-Request-Checklist
20+
21+
-->
22+
23+
> Please provide enough information so that others can review your pull request:
24+
25+
<!-- You can skip this if you're fixing a typo or updating existing documentation -->
26+
27+
> Explain the **details** for making this change. What existing problem does the pull request solve?
28+
29+
<!-- Example: When "Adding a function to do X", explain why it is necessary to have a way to do X. -->
30+
31+
> Screenshots/GIFs
32+
33+
<!-- Add images/recordings to better visualize the change: expected/current behviour -->
6.58 KB
Loading
4.16 KB
Loading

0 commit comments

Comments
 (0)