Skip to content
Open
Show file tree
Hide file tree
Changes from 250 commits
Commits
Show all changes
10000 commits
Select commit Hold shift + click to select a range
0d0c558
Home page break issue fix, landing page css fix (#1487)
nabeelmd-eGov Oct 9, 2024
09463f0
side bar mobileview and sidebar link order fixes (#1481)
mithunhegde-egov Oct 9, 2024
b657e8e
left logo top bar (#1492)
mithunhegde-egov Oct 10, 2024
9aa803e
fix tenant issue in pgr complaint (#1491)
aaradhya-egov Oct 10, 2024
0209ae1
Sidebar localization (#1494)
mithunhegde-egov Oct 10, 2024
28d9df2
home icon citizen (#1500)
mithunhegde-egov Oct 11, 2024
f24226a
User Token cache remove for multiroottenant and css fix (#1506)
nabeelmd-eGov Oct 11, 2024
d7f6ffc
shp-svg icon added (#1514)
suryansh-egov Oct 14, 2024
51f8e4d
fixed redirection issue (#1527)
Swathi-eGov Oct 15, 2024
af0239e
updated forgotpassword screen (#1532)
Swathi-eGov Oct 16, 2024
05333ea
side bar faq-component changes (#1534)
aaradhya-egov Oct 16, 2024
146b766
Role screen (#1535)
mithunhegde-egov Oct 17, 2024
6c3c51a
language enabled for sandbox (#1540)
aaradhya-egov Oct 17, 2024
37e1495
Css button fix (#1542)
mithunhegde-egov Oct 17, 2024
e94bec4
change language component added localization (#1543)
aaradhya-egov Oct 17, 2024
6fa1273
fixe the faq component added link in it (#1554)
aaradhya-egov Oct 18, 2024
cf96ea8
updated all the core package versions
jagankumar-egov Oct 18, 2024
fd7ff74
updated the library versions
jagankumar-egov Oct 18, 2024
403a6b9
Landing screen fixes (#1561)
mithunhegde-egov Oct 18, 2024
bdb9943
added city logic for multi root tenant (#1565)
aaradhya-egov Oct 18, 2024
464357c
VIEW COMPOSER ENHANCE FOR NO CARDSTYLE (#1567)
abishekTa-egov Oct 18, 2024
04a4d21
fix (#1571)
aaradhya-egov Oct 18, 2024
ec8808a
fix (#1572)
aaradhya-egov Oct 18, 2024
b43f9b6
how it works and user manual link added in the card (#1570)
mithunhegde-egov Oct 19, 2024
a26c1b6
updated backbutton to backlink (#1574)
Swathi-eGov Oct 19, 2024
d486681
role based home decoupled from modules (#1578)
mithunhegde-egov Oct 19, 2024
af16cb3
View composer fix (#1581)
abishekTa-egov Oct 19, 2024
51b0a0c
View composer fix (#1583)
abishekTa-egov Oct 19, 2024
573611d
added missing optional chaining (#1585)
mithunhegde-egov Oct 19, 2024
140f4ed
change the navigation logic in quick setup (#1592)
aaradhya-egov Oct 21, 2024
b47f4bb
fix on tetnant of pgr (#1594)
aaradhya-egov Oct 21, 2024
299e6f5
Hrms emp deactivate (#1589)
mithunhegde-egov Oct 21, 2024
a428e40
mobile sidebar redirection and cleanup of the sidebar redundant eleme…
mithunhegde-egov Oct 21, 2024
f7f79b3
fix of localisation (#1601)
aaradhya-egov Oct 21, 2024
814da8f
role landing url updated (#1603)
mithunhegde-egov Oct 21, 2024
c9f8d70
feedback changes- citizen sidebar login page and loader time increase…
mithunhegde-egov Oct 22, 2024
5006b5e
fix :: PGR localisty fixes (#1613)
aaradhya-egov Oct 22, 2024
3107594
Citizen sidebar cache (#1620)
mithunhegde-egov Oct 22, 2024
ed4a165
added localization for parent keys in sidebar (#1624)
Swathi-eGov Oct 23, 2024
f394ec7
build issue fix
jagankumar-egov Oct 23, 2024
ef8606f
citizen logout redirection handled in multiroot tenant (#1633)
mithunhegde-egov Oct 23, 2024
6564f90
Sandbox css fix on tooltips (#1636)
aaradhya-egov Oct 23, 2024
87190fe
branch name validators
jagankumar-egov Oct 23, 2024
f116a19
templates updated
jagankumar-egov Oct 23, 2024
6bc046f
updated the guidelines
jagankumar-egov Oct 23, 2024
68b5b2e
Update branch-name-check.yml
jagankumar-egov Oct 23, 2024
f228527
hrms edit and deactivate bug fixes (#1655)
mithunhegde-egov Oct 24, 2024
4dd7d5a
Updated the loader with text styles (#1735)
jagankumar-egov Nov 5, 2024
2781ed3
added support to customize url in iframe interface (#1736)
prerna-egov Nov 5, 2024
4e81618
Enhanced Inbox component to have dynamic svg icon from svg library (…
Swathi-eGov Nov 8, 2024
467cf06
updated the components version and made the employee module card updates
jagankumar-egov Nov 16, 2024
4276a66
updated the dss full module card component
jagankumar-egov Nov 16, 2024
b9663e8
Core module & Workbench Updated to have new Landing pacge card comp …
jagankumar-egov Nov 18, 2024
e2aea96
version updated
jagankumar-egov Nov 18, 2024
408518b
Updated the core wrapper module verison (#1849)
jagankumar-egov Nov 18, 2024
c5c6adb
version updated for core module
jagankumar-egov Nov 18, 2024
02b1cf2
Updated the components version
jagankumar-egov Nov 18, 2024
2a3f1cb
Updated the components & css version of core components
jagankumar-egov Nov 19, 2024
8127d65
Version updated for the components (#1856)
jagankumar-egov Nov 19, 2024
ae5621f
Updated the libraries version to 1.8.4
jagankumar-egov Nov 19, 2024
6b6153b
Updated only react component version
jagankumar-egov Nov 19, 2024
f04216f
Updated the module versions to 1.8.10
jagankumar-egov Nov 19, 2024
abe90e6
[1.0.11]
jagankumar-egov Nov 22, 2024
5f92adf
## [1.8.5] [26-Nov-2024]
jagankumar-egov Nov 26, 2024
d2b9df9
added comments for the usgae of field id
jagankumar-egov Nov 26, 2024
24b7d71
## [1.8.11] [26-Nov-2024] - Republished with new component version i…
jagankumar-egov Nov 26, 2024
fb39080
updated the version of libraries
jagankumar-egov Nov 26, 2024
a3510a1
FEATURE/HCMPRE-1447 added icons for microplan and updated versions (#…
Swathi-eGov Dec 12, 2024
77b0fde
updated versions (#2016)
Swathi-eGov Dec 12, 2024
87ba1e9
FEATURE/DPG-1634 updated versions (#2019)
Swathi-eGov Dec 13, 2024
882a9f8
FIX : Branch name validator fixed #2042
jagankumar-egov Dec 16, 2024
64ea409
FEATURE/HCMPRE-1642 : Show TotalCount next to tab name in UI (#2043)
abishekTa-egov Dec 16, 2024
28af811
BUGFIX/HCMPRE-1505 : Added dynamic regex validation for profile updat…
Swathi-eGov Dec 17, 2024
0909bb7
BUGFIX/SN-345 : Fixes setup master button bug (#2045)
aaradhya-egov Dec 17, 2024
5fd65e6
BUGFIX/DPG-1505 : Fixed Validation Issue on profile update (#2046)
Swathi-eGov Dec 17, 2024
d4664df
BUGFIX/SN-360 : Fixed localization issue (#2049)
aaradhya-egov Dec 17, 2024
3e232b1
BUGFIX/SN-388 : fixed tenant issue in complaint type (#2077)
aaradhya-egov Dec 26, 2024
0113cea
FEATURE/SN-390 : bulk button diable for adding master (#2083)
aaradhya-egov Dec 27, 2024
002f3e7
BUGFIX/SN-391 : complaint subtype fix (#2085)
aaradhya-egov Dec 27, 2024
5e2fe14
BUGFIX/SN-352 : making account name to max 60 length (#2086)
aaradhya-egov Dec 27, 2024
629d3ef
FEATURE/SN-368 : Workbench module enahancement to have auto localisat…
mithunhegde-egov Jan 6, 2025
8cfed3e
BUGFIX/HCMPRE-1866 : Css fix for pagination (#2125)
Swathi-eGov Jan 10, 2025
9a44df1
FEATURE/HCMPRE-1955 : Removing the usage of DIGIT-UI-CONTEXTS in libr…
Swathi-eGov Jan 21, 2025
b00a7f6
FEATURE/HCMPRE-1852 :: accessibility issues of image(#2120)
jagankumar-egov Jan 23, 2025
8d6ae99
FEATURE/HCMPRE-1852 :: accessibility issues of image
jagankumar-egov Jan 23, 2025
13fb1af
FEATURE/HCMPRE-1852 :: accessibility issues of dropdown & checkbox
jagankumar-egov Jan 23, 2025
835c717
BUGFIX/HCMPRE-1852 :: Fixed some console logs
jagankumar-egov Jan 23, 2025
5194677
BUGFIX/HCMPRE-0000 : fixed import issues of new ui-components (#2153)
Swathi-eGov Jan 23, 2025
c70d53a
FEATURE/HCMPRE-0001 : added svg-components as dependency for core mod…
Swathi-eGov Jan 24, 2025
922460d
BUGFIX/HCMPRE-0007: Stablized develop branch (#2145)
nipunarora-eGov Jan 29, 2025
13efcf8
FEATURE/HCMPRE-1425 : Added the workbench module patches and Updated …
Swathi-eGov Feb 1, 2025
d1f8ecd
FEATURE/HCMPRE-2208 :: Fixed the default landing for the unsupported …
jagankumar-egov Feb 3, 2025
c679afd
FEATURE/HCMPRE-1852 : POC for single landing ui for users
jagankumar-egov Feb 3, 2025
53e7028
FEATURE/HCMPRE-1852 : POC for single landing, Integrated the utiltiti…
jagankumar-egov Feb 5, 2025
53672eb
FEATURE/DUCE-230 : Added PGR, Core and miscellaneous fixes done in et…
Tulika-eGov Feb 5, 2025
d1435cf
BUGFIX/SN-406: changed validation length (#2213)
aaradhya-egov Feb 13, 2025
a942ad3
FEATURE/DPG-0000 : Added id prop for Privacy Component Checkbox (#2214)
Swathi-eGov Feb 13, 2025
54e69cc
FEATURE/DPG-0001 : Updated Core Module Version (#2215)
Swathi-eGov Feb 13, 2025
9201bb3
FEATURE/DUCE-244 : - Intergrated with react json editor and provided …
jagankumar-egov Feb 19, 2025
51d1a70
FEATURE/DUCE-244 : - Intergrated with react json editor CSS updated
jagankumar-egov Feb 19, 2025
8245c6b
MISC : Updated the Branch name validator logic to enable DUCE Projects
jagankumar-egov Feb 20, 2025
159a200
BUGFIX/DUCE-244: Fixed the build issue by incrementing all the depend…
jagankumar-egov Feb 21, 2025
61f9b8b
BUGFIX/SN-407: fixed pgr screen issue (#2233)
aaradhya-egov Feb 21, 2025
f2445a2
FEATURE/HCMPRE-2235 : Updated key (#2235)
Swathi-eGov Feb 21, 2025
e6b02ad
BUGFIX/SN-375 : edit profile alignment fixed in sandbox (#2236)
mithunhegde-egov Feb 21, 2025
2e840db
BUGFIX/SN-375 : updated css to override existing css changes for user…
mithunhegde-egov Feb 25, 2025
0b7d0b2
BUGFIX/SN-409: continue button disabled untill both checkbox and emai…
mithunhegde-egov Feb 25, 2025
9261086
FEATURE/DUCE-235 : integrated with json-edit-react for MDMS screens (…
Bhavya-egov Feb 25, 2025
a30461a
BUGFIX/SN-162 : Citizen otp fix in the Login page.
jagankumar-egov Feb 27, 2025
4a5ddce
BUGFIX/DUCE-235 : integrated with json-edit-react for MDMS
jagankumar-egov Feb 27, 2025
9b97795
BUGFIX/SN-162 : Citizen sms otp fix
jagankumar-egov Feb 27, 2025
4f930f4
BUGFIX/SN-411: user profile edit alignment changes in the app wrapper…
mithunhegde-egov Feb 27, 2025
438041f
BUGFIX/SN-412:fixed the user profile in citizen as it was breaking wi…
mithunhegde-egov Feb 28, 2025
73f91f7
BUGFIX/SN-413:panel card issue fixed in create employee as it was bre…
mithunhegde-egov Mar 3, 2025
8a76437
BUGFIX/DUCE-235 : Disabled json-edit-react & enable based on flag
jagankumar-egov Mar 3, 2025
7d565f3
FEATURE/DUCE-254 : Citizen Form composer & playground for the same (#…
jagankumar-egov Mar 4, 2025
d446157
FEATURE/DUCE-253 : Intergrated with react json editor for citizen for…
jagankumar-egov Mar 4, 2025
7cc8d5d
BUGFIX/DUCE-243 : Updated breadcrumb and regex validation mapping in …
Swathi-eGov Mar 7, 2025
cc95b45
FEATURE/DUCE-246:Login Screen trim the UserName (#2261)
abishekTa-egov Mar 10, 2025
bf74b24
FEATURE/DUCE-246:Userprofile password trimming (#2265)
abishekTa-egov Mar 10, 2025
af2126a
FEATURE/HCMPRE-2395 : added function to remove localisation cache (#2…
Bhavya-egov Mar 13, 2025
b7d4cf6
FEATURE/DUCE-234 : Enhancements in Localization Add Screen Bulk Uploa…
Swathi-eGov Mar 25, 2025
ed9c29f
CCSD-57: updated the new landing page config (#2288)
Tulika-eGov Mar 26, 2025
c5c30aa
FEATURE/DUCE-242:: sidebar items made configurable from ui (#2250)
suryansh-egov Apr 8, 2025
ef248df
CCSD-57 : added the static screens and local config for license modul…
Tulika-eGov Apr 9, 2025
b5db223
BUGFIX/CCSD-57-BRANCH-3: Used new version of core module: (#2318)
mukund-egov Apr 10, 2025
0af87b0
BUGFIX/CCSD-57-BRANCH-4:: Used new version of libraries and sandbox (…
mukund-egov Apr 10, 2025
ead3b72
fixed by adding newest version of core module in sandbox (#2323)
mukund-egov Apr 10, 2025
19fc281
BUGFIX/CCSD-167 :: Sandbox bugs on breadcrumbs and cleanup (#2339)
mukund-egov Apr 16, 2025
99a3333
Breadcrumb issues solved in HRMS and Core (Sandbox environment) (#2341)
mukund-egov Apr 16, 2025
bec24be
FEATURE/HCMPRE-2222 :: added 2 svg icons newWindow and GlobeLocationP…
Bhavya-egov Apr 21, 2025
aa848c6
FEATURE/HCMPRE-2222 : Incremented react-components version (#2350)
Bhavya-egov Apr 21, 2025
b186cfd
Solution Framework : Updated the custom mutation hook to handle custo…
Tulika-eGov Apr 25, 2025
5abd6c7
FEATURE/HCMPRE-0000 : Updated SheetName and Column Widths (#2380)
Swathi-eGov Apr 28, 2025
c219c4f
FEATURE/HCMPRE-2332 : added 2 new icons outpatient_med and ad_units (…
Bhavya-egov Apr 30, 2025
8b40dc4
FEATURE/HCMPRE-11::added 2 new icons (#2412)
Bhavya-egov May 13, 2025
c921ae9
BUGFIX/HCMPRE-2588:: removed mask from upload cloud svg (#2419)
Bhavya-egov May 13, 2025
51e8d80
BUGFIX/CCSD-185::updated packages for digit-ui-components (#2435)
Kamalesh-egov May 20, 2025
ef0e0ce
BUGFIX/CCSD-185 :: revert the component versions (#2458)
Kamalesh-egov May 27, 2025
b51a4af
BUGFIX/CCSD-216::privacy component alignment fix (#2460)
Kamalesh-egov May 27, 2025
b26a0d4
HCMPRE-2496: Develop carousel login screen revamp (#2488)
piyushraj-egov Jun 5, 2025
8fc8669
HCMPRE-2496:: - Added `Carousel.scss` for login screen CSS
jagankumar-egov Jun 5, 2025
412445e
Added Tutorial Guide SVG component (#2524)
Ramkrishna-egov Jun 9, 2025
bfb79b0
Imported Tutorial Guide svg component (#2527)
Ramkrishna-egov Jun 9, 2025
5851e07
HCMPRE-2496: [1.8.21] [10-Jun-2025] - integrated with updated version
jagankumar-egov Jun 10, 2025
d900890
HCMPRE-2496: [1.8.38] [10-Jun-2025]] - integrated with updated version
jagankumar-egov Jun 10, 2025
845a010
HCMPRE-2496: Develop carousel login screen revamp fixed (#2505)
piyushraj-egov Jun 11, 2025
b8742ca
HCMPRE-2496: Develop carousel login updated versions
jagankumar-egov Jun 11, 2025
73fe27f
HCMPRE-2496: Develop carousel login css versions updated (#2564)
jagankumar-egov Jun 11, 2025
4d6e07c
minor css update for forgot password (#2569)
piyushraj-egov Jun 12, 2025
4de31e4
HCMPRE-2496: - provided download of al data per schema 'ENABLE_MDMS_…
jagankumar-egov Jun 12, 2025
901c807
HCMPRE-2496: - version increment
jagankumar-egov Jun 12, 2025
c2b09c0
HCMPRE-2496: - version increments
jagankumar-egov Jun 12, 2025
3405d1a
HCMPRE-2496: ## [1.8.40] [11-Jun-2025] - Added module name config f…
jagankumar-egov Jun 12, 2025
c8b2872
HCMPRE-2496: ## [1.8.40] [11-Jun-2025] - Workbench download disabled …
jagankumar-egov Jun 12, 2025
8639afd
HCMPRE-2496: Develop feature forgot password (#2573)
piyushraj-egov Jun 12, 2025
16ce7a0
HCMPRE-2496: Adhoc feature to download & upload of the schema & login…
jagankumar-egov Jun 18, 2025
cd74a7c
[1.8.16] [20-Jun-2025]
jagankumar-egov Jun 20, 2025
3aa0ba4
FEATURE/DUCE-0000 : Checking useCustomAPIHook with the new version (#…
Swathi-eGov Jun 26, 2025
0656fe4
added new icon (#2687)
Bhavya-egov Jun 29, 2025
38b9b93
Sandbox-ui-icons updated (#2691)
Hari-egov Jun 30, 2025
01cb9e4
Fixed Version issue for publishing
jagankumar-egov Jul 1, 2025
d944373
Sandbox login page (#2644)
jagankumar-egov Jul 1, 2025
1d054f0
HRMS 1.8.13 and Core 1.8.44 Release PGR - DEMO Changes (#2788)
Hari-egov Jul 15, 2025
5e5c3fe
Pgr demo build (#2796)
Hari-egov Jul 15, 2025
1d94eab
Package publish Issue Fix (#2798)
Hari-egov Jul 15, 2025
cdbe37d
FEATURE/DUCE-0001 : Checking libraries with uicomponents as dependenc…
Swathi-eGov Jul 21, 2025
2d2bd87
Pgr hrms changes (#2860)
Hari-egov Jul 24, 2025
a68f7f1
Hrms pgr (#2869)
Hari-egov Jul 25, 2025
22bae4a
Hrms pgr 2 (#2870)
Hari-egov Jul 25, 2025
7d86814
Ccsd 528 (#2893)
Hari-egov Jul 29, 2025
f13a3c7
CCSD-508 merge (#2919)
Hari-egov Jul 31, 2025
ed75917
Language selection css sandbox (#2951)
syedkaifegov Aug 4, 2025
9059a2c
Feature/[1.8.19] [5-Aug-2025]
jagankumar-egov Aug 5, 2025
7ebfc97
[1.8.23] [6-Aug-2025]
jagankumar-egov Aug 6, 2025
cb3c9ad
[1.8.24] [6-Aug-2025]
jagankumar-egov Aug 6, 2025
2961318
Ccsd 622 474 458 (#2999)
Hari-egov Aug 12, 2025
d3774de
Develop (#3003)
syedkaifegov Aug 14, 2025
d9ed451
Employee margin fix (#3012)
syedkaifegov Aug 19, 2025
70444a5
Toast error message width issue fix (#3030)
salaudeenegov Aug 25, 2025
29afdda
FEATURE/HCMPRE-1123: Added iframe support and updated demo path (#3045)
abishekTa-egov Aug 26, 2025
8d05547
Ws css fix (#3047)
syedkaifegov Aug 26, 2025
8265698
BUGFIX/HCMPRE-1111 : Testing with new PDF Download Logic (#3160)
Swathi-eGov Sep 3, 2025
cafb392
BUGFIX/HCMPRE-1112 : Testing different PDF Download logics (#3161)
Swathi-eGov Sep 3, 2025
caebba5
BUGFIX/HCMPRE-1113 : Checking PDF Download Issue (#3162)
Swathi-eGov Sep 3, 2025
7f67c64
FEATURE/HCMPRE-0000 : Updated libraries and core version for stabilit…
Swathi-eGov Sep 8, 2025
b58336c
FEATURE/DUCE-287 : Added new logic for language selection page (#3210)
Swathi-eGov Sep 15, 2025
cf2c21d
Sandbox landing page merge develop (#3226)
Hari-egov Sep 22, 2025
cecb8c9
Studio hrms fix (#3231)
Tulika-eGov Sep 24, 2025
94b3a2e
CCSD-1077 : updated the login page to handle email based login (#3243)
Tulika-eGov Oct 3, 2025
9bb68c2
Corrected the order of usememo code (#3250)
Tulika-eGov Oct 3, 2025
1fd322b
Ccsd 1077 studio 2 (#3251)
Tulika-eGov Oct 3, 2025
13f4234
extend react-app error fix
piyushraj-egov Oct 5, 2025
5d3a1bc
vesrsions upgraded for all across app
piyushraj-egov Oct 5, 2025
be65ebd
fixed index.js for getStateId error(Digit error)
piyushraj-egov Oct 5, 2025
fd9932a
login disable fix(temporary)
piyushraj-egov Oct 6, 2025
57a038d
CCSD-1077 : updated the component to handle the redirection issue and…
Tulika-eGov Oct 6, 2025
f7cb90d
hrmscard null fix
piyushraj-egov Oct 7, 2025
743a5d2
build.yml added
piyushraj-egov Oct 7, 2025
e60ed91
skipped changelog updated
piyushraj-egov Oct 7, 2025
8ffec71
build yml file changes
piyushraj-egov Oct 7, 2025
a6808b2
BUGFIX/DUCE-0000 : Added fix for privacy policy error (#3257)
Swathi-eGov Oct 7, 2025
b44e4cb
install-deps changes for build
piyushraj-egov Oct 7, 2025
06d703c
CCSD-1077 : Updated the logic to include dynamic loginc component bel…
Tulika-eGov Oct 8, 2025
b8c6963
CCSD-1077: Updated the component to fix validation and style issue (#…
Tulika-eGov Oct 9, 2025
d96c9cc
removed comments and console logs
piyushraj-egov Oct 9, 2025
c0afc30
renamed to yaml
piyushraj-egov Oct 9, 2025
f2453ac
updated dockerfile node image
piyushraj-egov Oct 9, 2025
23ca2a6
trigger wf
piyushraj-egov Oct 9, 2025
5cbbce6
dynamic import in web to fix Digit error
piyushraj-egov Oct 10, 2025
62e39cd
index.js changes
piyushraj-egov Oct 10, 2025
2fb6894
CCSD-1107: Updated the email and mobilenumber login flow with pattern…
Tulika-eGov Oct 10, 2025
b6d3620
Revert "index.js changes"
piyushraj-egov Oct 10, 2025
3e4836f
svg comp added
piyushraj-egov Oct 10, 2025
7ce5411
App.js changes
piyushraj-egov Oct 10, 2025
0dcd0b3
enabled workbench
piyushraj-egov Oct 10, 2025
27f75cc
console logs removed, sandbox module revert
piyushraj-egov Oct 13, 2025
d040877
Merge branch 'develop' into develop-sub
jagankumar-egov Oct 13, 2025
8567fb8
coderabbit minor issues resolved
piyushraj-egov Oct 14, 2025
4201446
1100-BUGFIXES
piyushraj-egov Oct 17, 2025
6fbed44
added OVERRIDE_ROOT_TENANT_WITH_LOGGEDIN_TENANT to support multiple t…
jagankumar-egov Oct 22, 2025
b48719d
fixes added
jagankumar-egov Oct 22, 2025
4956abb
added fixes
jagankumar-egov Oct 22, 2025
a273eff
Merge branch 'develop-loc' into develop-sub
jagankumar-egov Oct 22, 2025
9fbc07d
fixes on the core for logo
jagankumar-egov Oct 22, 2025
256c80c
css
jagankumar-egov Oct 23, 2025
65a5f9e
updated manage master screen
jagankumar-egov Oct 23, 2025
3757dde
added filter
jagankumar-egov Oct 23, 2025
85f63e2
Update micro-ui/web/micro-ui-internals/packages/modules/core/src/comp…
jagankumar-egov Oct 23, 2025
7c7dbd2
removed console.logs
jagankumar-egov Oct 23, 2025
bfad6ab
Updated some fixes in workbench screens
jagankumar-egov Oct 23, 2025
4a4048c
updated with new version
jagankumar-egov Oct 23, 2025
b51452e
Updated the changelogs
jagankumar-egov Oct 23, 2025
ffd2949
updated version
jagankumar-egov Oct 23, 2025
6ee192a
Updated the changelogs
jagankumar-egov Oct 24, 2025
14fd1b8
Update CHANGELOG.md
jagankumar-egov Oct 24, 2025
cf1e5ac
updated readme
jagankumar-egov Oct 24, 2025
04a7179
updated
jagankumar-egov Oct 24, 2025
4517f50
added readme
jagankumar-egov Oct 24, 2025
1691d28
updaeted readme
jagankumar-egov Oct 24, 2025
56145d8
publish for an rc build before release
jagankumar-egov Oct 27, 2025
06777e8
Update package.json
jagankumar-egov Oct 27, 2025
093f19b
Update publish-workbench.sh
jagankumar-egov Oct 27, 2025
2ac4c63
Test core ui build
jagankumar-egov Oct 27, 2025
b871852
updated workbench build
jagankumar-egov Oct 27, 2025
a7a1dd3
updated dependency versions
jagankumar-egov Oct 27, 2025
cea8fb0
fixes for build
jagankumar-egov Oct 27, 2025
de763c6
updated to packages
jagankumar-egov Oct 27, 2025
b8e67c7
Update index.html
jagankumar-egov Oct 27, 2025
351115c
updated fixes for build
jagankumar-egov Oct 27, 2025
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
The table of contents is too big for display.
Diff view
Diff view
  •  
  •  
  •  
16 changes: 16 additions & 0 deletions .github/PULL_REQUEST_TEMPLATE/bugfix_template.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
### Bugfix Request
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick | 🔵 Trivial

Consider using a top-level heading.

Markdown convention suggests the first heading should be level 1 (#) rather than level 3 (###).

Apply this diff:

-### Bugfix Request
+# Bugfix Request
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
### Bugfix Request
# Bugfix Request
🧰 Tools
🪛 LanguageTool

[grammar] ~1-~1: Ensure spelling is correct
Context: ### Bugfix Request #### JIRA ID <!-- Provide a de...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

🪛 markdownlint-cli2 (0.18.1)

1-1: First line in a file should be a top-level heading

(MD041, first-line-heading, first-line-h1)

🤖 Prompt for AI Agents
.github/PULL_REQUEST_TEMPLATE/bugfix_template.md around lines 1 to 1: The
template currently starts with a level-3 heading "### Bugfix Request"; change it
to a top-level level-1 heading by replacing the initial "###" with "#" so the
file begins with "# Bugfix Request" to follow Markdown convention.


#### JIRA ID
<!-- Provide a detailed description of the feature -->

#### Module
<!-- Provide a detailed description of the feature -->

#### Description
<!-- Provide a detailed description of the feature -->
Comment on lines +3 to +10
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Fix placeholder text to match bugfix context.

The placeholder comments for "JIRA ID," "Module," and "Description" all say "Provide a detailed description of the feature," which is incorrect for a bugfix template.

Apply this diff:

 #### JIRA ID
-<!-- Provide a detailed description of the feature -->
+<!-- Provide the JIRA bug ticket ID -->
 
 #### Module
-<!-- Provide a detailed description of the feature -->
+<!-- Specify the module or component with the bug -->
 
 #### Description
-<!-- Provide a detailed description of the feature -->
+<!-- Provide a detailed description of the bug and the fix -->
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
#### JIRA ID
<!-- Provide a detailed description of the feature -->
#### Module
<!-- Provide a detailed description of the feature -->
#### Description
<!-- Provide a detailed description of the feature -->
#### JIRA ID
<!-- Provide the JIRA bug ticket ID -->
#### Module
<!-- Specify the module or component with the bug -->
#### Description
<!-- Provide a detailed description of the bug and the fix -->
🤖 Prompt for AI Agents
In .github/PULL_REQUEST_TEMPLATE/bugfix_template.md around lines 3 to 10, the
placeholder helper text incorrectly references "feature" for the JIRA ID,
Module, and Description fields; update those placeholders to reference "bug" or
"bugfix" context (e.g., "Provide the JIRA ID for the bug", "Provide the module
affected by the bug", "Provide a detailed description of the bug and steps to
reproduce") so the template accurately guides bugfix PR authors.


### Root Cause
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Make heading level consistent.

"Root Cause" uses heading level 3 (###) while other sections use level 4 (####). This inconsistency should be corrected.

Apply this diff:

-### Root Cause
+#### Root Cause
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
### Root Cause
#### Root Cause
🤖 Prompt for AI Agents
In .github/PULL_REQUEST_TEMPLATE/bugfix_template.md around line 12, the "Root
Cause" heading is level 3 (###) while other sections use level 4 (####); change
the heading to level 4 (#### Root Cause) so all section headings use the same
level.

<!-- Describe the root cause of the bug. -->

#### Related Issues
<!-- Link any related GitHub issues here -->
13 changes: 13 additions & 0 deletions .github/PULL_REQUEST_TEMPLATE/feature_template.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
### Feature Request
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick | 🔵 Trivial

Consider using a top-level heading.

Markdown convention suggests the first heading in a file should be level 1 (#) rather than level 3 (###).

Apply this diff:

-### Feature Request
+# Feature Request
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
### Feature Request
# Feature Request
🧰 Tools
🪛 markdownlint-cli2 (0.18.1)

1-1: First line in a file should be a top-level heading

(MD041, first-line-heading, first-line-h1)

🤖 Prompt for AI Agents
.github/PULL_REQUEST_TEMPLATE/feature_template.md around line 1: the file starts
with a level-3 heading ("### Feature Request"); change it to a top-level level-1
heading by replacing the leading "###" with a single "#" so the first heading
follows Markdown convention and is rendered as the document title.


#### JIRA ID
<!-- Provide a detailed description of the feature -->

#### Module
<!-- Provide a detailed description of the feature -->
Comment on lines +3 to +7
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Fix placeholder text to match section context.

The placeholder comments for "JIRA ID" and "Module" sections both say "Provide a detailed description of the feature," which is misleading. Each section should have contextually appropriate guidance.

Apply this diff:

 #### JIRA ID
-<!-- Provide a detailed description of the feature -->
+<!-- Provide the JIRA ticket ID (e.g., HCMPRE-1234) -->
 
 #### Module
-<!-- Provide a detailed description of the feature -->
+<!-- Specify the module or component affected (e.g., HRMS, PGR) -->
🤖 Prompt for AI Agents
.github/PULL_REQUEST_TEMPLATE/feature_template.md around lines 3 to 7: the
placeholder guidance for the "JIRA ID" and "Module" sections is incorrect and
duplicates "Provide a detailed description of the feature"; update the
placeholders to give contextually appropriate guidance by replacing the JIRA ID
comment with something like "Enter related JIRA ticket identifier (e.g.,
PROJ-123)" and the Module comment with guidance like "Specify the
code/module/area this feature touches (e.g., auth-service)", ensuring concise,
context-specific instructions for each section.


#### Description
<!-- Provide a detailed description of the feature -->

#### Related Issues
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Remove trailing whitespace.

Line 12 has trailing whitespace that should be removed for clean markdown formatting.

Apply this diff:

-#### Related Issues 
+#### Related Issues
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
#### Related Issues
#### Related Issues
🧰 Tools
🪛 markdownlint-cli2 (0.18.1)

12-12: Trailing spaces
Expected: 0 or 2; Actual: 1

(MD009, no-trailing-spaces)

🤖 Prompt for AI Agents
In .github/PULL_REQUEST_TEMPLATE/feature_template.md around line 12, there is
trailing whitespace at the end of the "#### Related Issues" line; remove the
trailing space(s) so the markdown line ends immediately after the text (no extra
spaces or tabs) to ensure clean formatting and no trailing whitespace in the
file.

<!-- Link any related GitHub issues here -->
16 changes: 16 additions & 0 deletions .github/PULL_REQUEST_TEMPLATE/release_template.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
### Release Request
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick | 🔵 Trivial

Consider using a top-level heading.

Markdown convention suggests the first heading should be level 1 (#) rather than level 3 (###).

Apply this diff:

-### Release Request
+# Release Request
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
### Release Request
# Release Request
🧰 Tools
🪛 markdownlint-cli2 (0.18.1)

1-1: First line in a file should be a top-level heading

(MD041, first-line-heading, first-line-h1)

🤖 Prompt for AI Agents
.github/PULL_REQUEST_TEMPLATE/release_template.md around line 1: the template
uses a level-3 heading ("### Release Request") but should follow Markdown
convention and use a top-level level-1 heading; change the heading to a single
"#" heading ("# Release Request") so the document begins with an H1.


#### JIRA ID
<!-- Provide a detailed description of the feature -->

#### Module
<!-- Provide a detailed description of the feature -->

#### Description
<!-- Provide a detailed description of the feature -->
Comment on lines +3 to +10
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Fix placeholder text to match release context.

The placeholder comments for "JIRA ID," "Module," and "Description" all say "Provide a detailed description of the feature," which is incorrect for a release template. They should reference release-specific information.

Apply this diff:

 #### JIRA ID
-<!-- Provide a detailed description of the feature -->
+<!-- Provide the JIRA release ticket ID -->
 
 #### Module
-<!-- Provide a detailed description of the feature -->
+<!-- Specify the modules included in this release -->
 
 #### Description
-<!-- Provide a detailed description of the feature -->
+<!-- Provide a detailed description of the release -->
🤖 Prompt for AI Agents
In .github/PULL_REQUEST_TEMPLATE/release_template.md around lines 3 to 10, the
placeholder helper text for the "JIRA ID", "Module", and "Description" fields is
incorrect (it currently reads "Provide a detailed description of the feature");
update each placeholder to reference release-specific guidance: replace the JIRA
ID placeholder with something like "Provide the release JIRA ticket or ID", the
Module placeholder with "Indicate the affected module(s) in this release", and
the Description placeholder with "Summarize the release changes, fixes, and
notes" so the template reflects release context.


#### List of Features
<!-- Link any related GitHub issues here -->

#### List of Issues
Comment on lines +12 to +15
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Remove trailing spaces.

Lines 12 and 15 have trailing spaces, which violate markdown formatting standards.

Apply this diff:

-#### List of Features 
+#### List of Features
 <!-- Link any related GitHub issues here -->
 
-#### List of Issues 
+#### List of Issues
🧰 Tools
🪛 markdownlint-cli2 (0.18.1)

12-12: Trailing spaces
Expected: 0 or 2; Actual: 1

(MD009, no-trailing-spaces)


15-15: Trailing spaces
Expected: 0 or 2; Actual: 1

(MD009, no-trailing-spaces)

🤖 Prompt for AI Agents
.github/PULL_REQUEST_TEMPLATE/release_template.md around lines 12 to 15: remove
the trailing spaces at the ends of lines 12 and 15 so the markdown lines "####
List of Features" and "#### List of Issues" do not contain trailing whitespace;
update the file by trimming those two line endings (and run a quick linter/trim
whitespace check) and commit the change.

<!-- Link any related GitHub issues here -->
25 changes: 25 additions & 0 deletions .github/hooks/pre-push
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
#!/bin/sh

# Get the current branch name
BRANCH_NAME=$(git rev-parse --abbrev-ref HEAD)

# Define the pattern
PATTERN="^(FEATURE|BUGFIX|RELEASE)\/(HCMPRE|DPG|SN)-[0-9]{1,5}$"

# Check if the branch name matches the pattern
if [[ ! "$BRANCH_NAME" =~ $PATTERN ]]; then
Comment on lines +1 to +10
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

Fix shell compatibility issue.

The script uses #!/bin/sh (POSIX shell) but line 10 uses [[ ]], which is a bash-specific construct. This will fail on systems where /bin/sh is not bash (e.g., dash on Debian/Ubuntu).

Choose one solution:

Solution 1 (recommended): Change shebang to bash:

-#!/bin/sh
+#!/bin/bash

Solution 2: Use POSIX-compatible syntax:

-if [[ ! "$BRANCH_NAME" =~ $PATTERN ]]; then
+if ! echo "$BRANCH_NAME" | grep -Eq "$PATTERN"; then
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
#!/bin/sh
# Get the current branch name
BRANCH_NAME=$(git rev-parse --abbrev-ref HEAD)
# Define the pattern
PATTERN="^(FEATURE|BUGFIX|RELEASE)\/(HCMPRE|DPG|SN)-[0-9]{1,5}$"
# Check if the branch name matches the pattern
if [[ ! "$BRANCH_NAME" =~ $PATTERN ]]; then
#!/bin/bash
# Get the current branch name
BRANCH_NAME=$(git rev-parse --abbrev-ref HEAD)
# Define the pattern
PATTERN="^(FEATURE|BUGFIX|RELEASE)\/(HCMPRE|DPG|SN)-[0-9]{1,5}$"
# Check if the branch name matches the pattern
if [[ ! "$BRANCH_NAME" =~ $PATTERN ]]; then
Suggested change
#!/bin/sh
# Get the current branch name
BRANCH_NAME=$(git rev-parse --abbrev-ref HEAD)
# Define the pattern
PATTERN="^(FEATURE|BUGFIX|RELEASE)\/(HCMPRE|DPG|SN)-[0-9]{1,5}$"
# Check if the branch name matches the pattern
if [[ ! "$BRANCH_NAME" =~ $PATTERN ]]; then
#!/bin/sh
# Get the current branch name
BRANCH_NAME=$(git rev-parse --abbrev-ref HEAD)
# Define the pattern
PATTERN="^(FEATURE|BUGFIX|RELEASE)\/(HCMPRE|DPG|SN)-[0-9]{1,5}$"
# Check if the branch name matches the pattern
if ! echo "$BRANCH_NAME" | grep -Eq "$PATTERN"; then
🤖 Prompt for AI Agents
In .github/hooks/pre-push around lines 1 to 10 the script declares #!/bin/sh but
uses the bash-specific [[ ]] test which will fail on shells like dash; fix by
either changing the shebang to a bash interpreter (e.g., #!/usr/bin/env bash) so
[[ ]] is valid, or replace the [[ ]] test with POSIX-compatible logic (for
example use case, grep -E, or expr to match the branch name against the PATTERN)
and ensure any other bash-only constructs are removed.

echo "Branch name '$BRANCH_NAME' does not follow the correct pattern:"
echo " - FEATURE/HCMPRE-<TICKET_NO>"
echo " - FEATURE/DPG-<TICKET_NO>"
echo " - FEATURE/SN-<TICKET_NO>"
echo " - BUGFIX/HCMPRE-<TICKET_NO>"
echo " - BUGFIX/DPG-<TICKET_NO>"
echo " - BUGFIX/SN-<TICKET_NO>"
echo " - RELEASE/HCMPRE-<TICKET_NO>"
echo " - RELEASE/DPG-<TICKET_NO>"
Comment on lines +18 to +19
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Add missing RELEASE/SN example.

The pattern allows RELEASE/SN-<TICKET_NO> but this example is missing from the error message, creating an inconsistency.

Apply this diff:

   echo " - RELEASE/HCMPRE-<TICKET_NO>"
   echo " - RELEASE/DPG-<TICKET_NO>"
+  echo " - RELEASE/SN-<TICKET_NO>"
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
echo " - RELEASE/HCMPRE-<TICKET_NO>"
echo " - RELEASE/DPG-<TICKET_NO>"
echo " - RELEASE/HCMPRE-<TICKET_NO>"
echo " - RELEASE/DPG-<TICKET_NO>"
echo " - RELEASE/SN-<TICKET_NO>"
🤖 Prompt for AI Agents
In .github/hooks/pre-push around lines 18 to 19, the error/examples output lists
RELEASE/HCMPRE-<TICKET_NO> and RELEASE/DPG-<TICKET_NO> but omits the allowed
RELEASE/SN-<TICKET_NO> pattern; add a third echo line echo " -
RELEASE/SN-<TICKET_NO>" alongside the existing two so the message consistently
shows all permitted RELEASE patterns.

echo "Where <TICKET_NO> is a number between 0 and 99999."
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Correct the ticket number range in documentation.

The pattern {1,5} allows 1 to 5 digits (1-99999), not "0 and 99999" as stated. The documentation is misleading.

Apply this diff:

-echo "Where <TICKET_NO> is a number between 0 and 99999."
+echo "Where <TICKET_NO> is a 1-5 digit number (1-99999)."
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
echo "Where <TICKET_NO> is a number between 0 and 99999."
echo "Where <TICKET_NO> is a 1-5 digit number (1-99999)."
🤖 Prompt for AI Agents
In .github/hooks/pre-push around line 20, the comment "Where <TICKET_NO> is a
number between 0 and 99999." is incorrect because the regex {1,5} matches 1 to 5
digits (1–99999); update the wording to accurately state "Where <TICKET_NO> is a
number between 1 and 99999" (or "1–99999") so the documentation matches the
pattern.

exit 1
fi

# If the pattern matches, allow the push
exit 0
Comment on lines +1 to +25
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick | 🔵 Trivial

Ensure the hook actually runs and harden it.

  • Document or automate: git config core.hooksPath .github/hooks so this script executes.
  • Optional: if you adopt bash, add set -euo pipefail at the top.
🤖 Prompt for AI Agents
.github/hooks/pre-push lines 1-25: the hook currently may not run for
contributors and is not hardened; add documentation and an automated setup plus
tighten the script: document in CONTRIBUTING (or add a repo setup script) that
callers must run git config core.hooksPath .github/hooks (or run the provided
setup script) so the hook is actually installed, and modify the hook itself to
use a stricter shell and fail-fast behaviour by switching the shebang to bash if
you rely on bash features and adding safe flags (set -euo pipefail) or otherwise
keep POSIX sh-compatible logic; also ensure the branch-name regex check uses a
shell construct supported by the chosen shell (or use git rev-parse and grep -E
for portability) and keep the existing exit codes.

5 changes: 5 additions & 0 deletions .github/pull_request_template.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
## Choose the appropriate template for your PR:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick | 🔵 Trivial

Use a top‑level H1 for the first heading (markdownlint MD041).

Change the opening heading to H1.

-## Choose the appropriate template for your PR:
+# Choose the appropriate template for your PR:
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
## Choose the appropriate template for your PR:
# Choose the appropriate template for your PR:
🧰 Tools
🪛 markdownlint-cli2 (0.18.1)

1-1: First line in a file should be a top-level heading

(MD041, first-line-heading, first-line-h1)

🤖 Prompt for AI Agents
In .github/pull_request_template.md around line 1, the first heading is
currently a level-2 heading ("## Choose the appropriate template for your PR:")
which violates markdownlint MD041; change it to a top-level H1 by replacing the
leading "##" with "#" so the file begins with "# Choose the appropriate template
for your PR:" ensuring the very first heading in the document is H1.


- [Feature PR](./PULL_REQUEST_TEMPLATE/feature_template.md)
- [Bugfix PR](./PULL_REQUEST_TEMPLATE/bugfix_template.md)
- [Release PR](./PULL_REQUEST_TEMPLATE/release_template.md)
Comment on lines +1 to +5
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick | 🔵 Trivial

Add blank line after heading.

Markdown style guidelines recommend surrounding headings with blank lines for better readability.

Apply this diff:

 ## Choose the appropriate template for your PR:
+
 - [Feature PR](./PULL_REQUEST_TEMPLATE/feature_template.md)
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
## Choose the appropriate template for your PR:
- [Feature PR](./PULL_REQUEST_TEMPLATE/feature_template.md)
- [Bugfix PR](./PULL_REQUEST_TEMPLATE/bugfix_template.md)
- [Release PR](./PULL_REQUEST_TEMPLATE/release_template.md)
## Choose the appropriate template for your PR:
- [Feature PR](./PULL_REQUEST_TEMPLATE/feature_template.md)
- [Bugfix PR](./PULL_REQUEST_TEMPLATE/bugfix_template.md)
- [Release PR](./PULL_REQUEST_TEMPLATE/release_template.md)
🧰 Tools
🪛 markdownlint-cli2 (0.18.1)

3-3: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below

(MD022, blanks-around-headings)

🤖 Prompt for AI Agents
.github/pull_request_template.md around lines 1 to 5: the heading line "##
Choose the appropriate template for your PR:" is not followed by a blank line;
add a single blank line immediately after the heading so the markdown heading is
separated from the subsequent list for proper formatting and readability.

79 changes: 79 additions & 0 deletions .github/workflows/branch-name-check.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,79 @@
name: Branch and PR Name Validation

on:
push:
branches:
- master
- develop
- console

pull_request:
branches:
- master
- develop
- console

types:
- opened
- edited
- reopened

jobs:
validate-names:
runs-on: ubuntu-latest
steps:
- name: Checkout code
uses: actions/checkout@v3

- name: Validate branch name
run: |
# Determine the branch name
if [[ "${GITHUB_EVENT_NAME}" == "pull_request" ]]; then
branch_name="${GITHUB_HEAD_REF}"
else
branch_name="${GITHUB_REF#refs/heads/}"
fi

# Define the branch name pattern
PREFIXES="FEATURE|BUGFIX|RELEASE"
PROJECTS="HCMPRE|DPG|SN|DUCE"
TICKET_PATTERN="[0-9]{1,5}"
BRANCH_PATTERN="^($PREFIXES)\/($PROJECTS)-$TICKET_PATTERN$"

# Validate the branch name
if [[ ! "$branch_name" =~ $BRANCH_PATTERN ]]; then
echo "Branch name '$branch_name' does not follow the correct pattern: $PREFIXES/$PROJECTS-<TICKET_NO> where <TICKET_NO> is $TICKET_PATTERN"
exit 1
fi

- name: Validate PR title
if: ${{ github.event_name == 'pull_request' }} # Only for PR validation
run: |
# Define constants
PREFIXES="FEATURE|BUGFIX|RELEASE"
PROJECTS="HCMPRE|DPG|SN|DUCE"
TICKET_PATTERN="[0-9]{1,5}"
TITLE_PATTERN="^($PREFIXES)\/($PROJECTS)-$TICKET_PATTERN.*$"
MIN_TITLE_LENGTH=30


# Fetch the latest PR title dynamically
pr_title=$(curl -s https://api.github.com/repos/${{ github.repository }}/pulls/${{ github.event.pull_request.number }} | jq -r '.title')
echo "Fetched PR title: $pr_title"

# Validate the PR title
if [[ ! "$pr_title" =~ $TITLE_PATTERN ]]; then
echo "PR title '$pr_title' does not follow the correct pattern: $PREFIXES/$PROJECTS-<TICKET_NO> : <Description> where <TICKET_NO> is $TICKET_PATTERN"
exit 1
fi

# Validate the PR title length
if [[ ${#pr_title} -lt $MIN_TITLE_LENGTH ]]; then
echo "PR title '$pr_title' is too short. It must be at least $MIN_TITLE_LENGTH characters long, excluding the default pattern or ticket number."
exit 1
fi

echo "PR title validation passed."



Comment on lines +23 to +79

Check warning

Code scanning / CodeQL

Workflow does not contain permissions Medium

Actions job or workflow does not limit the permissions of the GITHUB_TOKEN. Consider setting an explicit permissions block, using the following as a minimal starting point: {contents: read}

Copilot Autofix

AI about 1 month ago

To address the problem, you should add a permissions block to the workflow to explicitly limit the permissions of the GITHUB_TOKEN granted to the job(s). As per best practice and the workflow's requirements, minimally the job requires read access to repository contents to allow actions/checkout to function, but does not need write access. There are also API calls to fetch PR details, but those only require permission to read metadata (which is covered by contents: read in this case). To fix, add a top-level permissions: section—just below the workflow's name: field—setting contents: read. If additional permission is later required (e.g., to write to issues or PRs), those should be added specifically. Edit .github/workflows/branch-name-check.yml to add the following block:

permissions:
  contents: read

This change should be made as a new block after the name: line (after line 1, before on:). No new imports or dependencies are required.

Suggested changeset 1
.github/workflows/branch-name-check.yml

Autofix patch

Autofix patch
Run the following command in your local git repository to apply this patch
cat << 'EOF' | git apply
diff --git a/.github/workflows/branch-name-check.yml b/.github/workflows/branch-name-check.yml
--- a/.github/workflows/branch-name-check.yml
+++ b/.github/workflows/branch-name-check.yml
@@ -1,4 +1,6 @@
 name: Branch and PR Name Validation
+permissions:
+  contents: read
 
 on:
   push:
EOF
@@ -1,4 +1,6 @@
name: Branch and PR Name Validation
permissions:
contents: read

on:
push:
Copilot is powered by AI and may make mistakes. Always verify output.
231 changes: 231 additions & 0 deletions .github/workflows/build.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,231 @@
name: Build Pipeline
run-name: Build ${{ github.event.inputs.pipeline_name }}

on:
workflow_dispatch:
inputs:
pipeline_name:
description: 'Name of the config pipeline to build and deploy'
required: true
type: choice
options:
- digit-ui
- core-ui
- workbench-ui
- sandbox-ui
- microplan-ui
- console
- dashboard-ui
- payments-ui
- storybook-svg
- storybook
- egov-bff
- core-digit-ui
- dss-ui
- hrms-ui
- karnataka-ui
- meghalaya-ui

env:
DOCKER_USERNAME: ${{ vars.DOCKER_USERNAME }}
DOCKER_PASSWORD: ${{ secrets.DOCKER_ACCESS_TOKEN }}

jobs:
resolve-config:
name: Resolve ${{ github.event.inputs.pipeline_name }} config
runs-on: ubuntu-latest
outputs:
work_dir: ${{ steps.setenv.outputs.work_dir }}
image_name: ${{ steps.setenv.outputs.image_name }}
dockerfile: ${{ steps.setenv.outputs.dockerfile }}
tag: ${{ steps.tag.outputs.tag }}
steps:
- name: Checkout Code
uses: actions/checkout@v3

- name: Install yq
run: |
VERSION="4.30.8"
URL="https://github.com/mikefarah/yq/releases/download/v${VERSION}/yq_linux_amd64"
sudo curl -sSL "$URL" -o /usr/local/bin/yq
sudo chmod +x /usr/local/bin/yq

- name: Resolve env from build-config.yml
id: setenv
run: |
PIPELINE_NAME="${{ github.event.inputs.pipeline_name }}"
DEFAULT_DOCKERFILE="Dockerfile"
echo "### Pipeline Name - $PIPELINE_NAME" >> $GITHUB_STEP_SUMMARY

# Find exactly one matching config block
MATCHING_CONFIGS=$(yq eval -o=json '.config[] | select(.name | test("/'"$PIPELINE_NAME"'$"))' build/build-config.yml)
MATCH_COUNT=$(echo "$MATCHING_CONFIGS" | jq -s 'length')
if [ "$MATCH_COUNT" -ne 1 ]; then
echo "ERROR: Expected exactly 1 matching pipeline config, but found $MATCH_COUNT"
exit 1
fi

# Extract fields
SERVICE_BUILD_CONFIG=$(echo "$MATCHING_CONFIGS" | jq -c '.build[] | select(.["image-name"])')
SERVICE_WORK_DIR=$(echo "$SERVICE_BUILD_CONFIG" | yq eval -r '.["work-dir"] // ""' -)
SERVICE_IMAGE_NAME=$(echo "$SERVICE_BUILD_CONFIG" | yq eval -r '.["image-name"] // ""' -)
SERVICE_DOCKERFILE=$(echo "$SERVICE_BUILD_CONFIG" | yq eval -r '.dockerfile // ""' -)

# Default Dockerfile if none specified
if [ -z "$SERVICE_DOCKERFILE" ]; then
SERVICE_DOCKERFILE="$SERVICE_WORK_DIR/$DEFAULT_DOCKERFILE"
fi

# Export
echo "SERVICE_WORK_DIR=$SERVICE_WORK_DIR" >> "$GITHUB_ENV"
echo "SERVICE_IMAGE_NAME=$SERVICE_IMAGE_NAME" >> "$GITHUB_ENV"
echo "SERVICE_DOCKERFILE=$SERVICE_DOCKERFILE" >> "$GITHUB_ENV"
echo "work_dir=$SERVICE_WORK_DIR" >> $GITHUB_OUTPUT
echo "image_name=$SERVICE_IMAGE_NAME" >> $GITHUB_OUTPUT
echo "dockerfile=$SERVICE_DOCKERFILE" >> $GITHUB_OUTPUT

# Put summary for the step
echo "#### Application Config Summary" >> $GITHUB_STEP_SUMMARY
echo "Application Work Directory - $SERVICE_WORK_DIR" >> $GITHUB_STEP_SUMMARY
echo "Image Name - $SERVICE_IMAGE_NAME" >> $GITHUB_STEP_SUMMARY
echo "Dockerfile Path - $SERVICE_DOCKERFILE" >> $GITHUB_STEP_SUMMARY

- name: Generate the Next Tag
id: tag
run: |
set -euxo pipefail
BRANCH="${GITHUB_REF##*/}"
COMMIT_HASH=$(git rev-parse --short HEAD)
SERVICE_NAME="${{ env.SERVICE_IMAGE_NAME }}"

TOKEN=$(curl -s -X POST "https://hub.docker.com/v2/users/login/" \
-H "Content-Type: application/json" \
-d "{\"username\": \"$DOCKER_USERNAME\", \"password\": \"$DOCKER_PASSWORD\"}" \
| jq -r .token)

if [ -z "$TOKEN" ]; then
echo "Failed to authenticate with Docker Hub." >&2
exit 1
fi

# Check if repo exists
HTTP_CODE=$(curl -s -o /dev/null -w '%{http_code}' \
-H "Authorization: JWT $TOKEN" \
"https://hub.docker.com/v2/repositories/$DOCKER_USERNAME/$SERVICE_NAME/")

if [ "$HTTP_CODE" -ne 200 ]; then
NEXT_TAG="${BRANCH}-${COMMIT_HASH}"
else
EXISTING_TAGS=$(curl -s -H "Authorization: JWT $TOKEN" \
"https://hub.docker.com/v2/repositories/$DOCKER_USERNAME/$SERVICE_NAME/tags?page_size=100" \
| jq -r '.results[].name')
LATEST_TAG=$(echo "$EXISTING_TAGS" \
| grep "^${BRANCH}-${COMMIT_HASH}" || true \
| sort -V \
| tail -n 1)
NEXT_TAG="${LATEST_TAG:-${BRANCH}-${COMMIT_HASH}}"
fi

echo "tag=$NEXT_TAG" >> "$GITHUB_OUTPUT"
echo "NEXT_TAG=$NEXT_TAG" >> "$GITHUB_ENV"
echo "tag - $NEXT_TAG" >> $GITHUB_STEP_SUMMARY

build-matrix:
Comment on lines +35 to +133

Check warning

Code scanning / CodeQL

Workflow does not contain permissions Medium

Actions job or workflow does not limit the permissions of the GITHUB_TOKEN. Consider setting an explicit permissions block, using the following as a minimal starting point: {contents: read}

Copilot Autofix

AI about 1 month ago

The problem is that the workflow does not declare a permissions key, and so uses the repository's default (potentially overly privileged) token permissions. To fix this, add a permissions block at the root of the workflow, just after the name/run-name keys and before on:. As the minimal safe default, set permissions: contents: read. If specific jobs require more, these can be expanded, but for the jobs and steps shown, contents: read (read-only access to the repository) is sufficient.

The change is a single addition to the top-level YAML keys in .github/workflows/build.yaml. No additional imports, methods, or new definitions are needed.


Suggested changeset 1
.github/workflows/build.yaml

Autofix patch

Autofix patch
Run the following command in your local git repository to apply this patch
cat << 'EOF' | git apply
diff --git a/.github/workflows/build.yaml b/.github/workflows/build.yaml
--- a/.github/workflows/build.yaml
+++ b/.github/workflows/build.yaml
@@ -1,5 +1,7 @@
 name: Build Pipeline
 run-name: Build ${{ github.event.inputs.pipeline_name }}
+permissions:
+  contents: read
 
 on:
   workflow_dispatch:
EOF
@@ -1,5 +1,7 @@
name: Build Pipeline
run-name: Build ${{ github.event.inputs.pipeline_name }}
permissions:
contents: read

on:
workflow_dispatch:
Copilot is powered by AI and may make mistakes. Always verify output.
name: Build application ${{ matrix.arch }}
needs: [resolve-config]
strategy:
matrix:
include:
- arch: amd64
platform: linux/amd64
runner: ubuntu-latest
- arch: arm64
platform: linux/arm64
runner: ubuntu-24.04-arm
runs-on: ${{ matrix.runner }}
outputs:
amd64_digest: ${{ steps.digest_amd64.outputs.digest }}
arm64_digest: ${{ steps.digest_arm64.outputs.digest }}
steps:
- name: Checkout Code
uses: actions/checkout@v3

- name: Set up Docker Buildx
uses: docker/setup-buildx-action@v3

- name: Cache Docker Layers
uses: actions/cache@v3
with:
path: /tmp/.buildx-cache
key: ${{ runner.os }}-${{ matrix.arch }}-buildx-${{ github.event.inputs.pipeline_name }}-${{ github.ref_name }}
restore-keys: |
${{ runner.os }}-${{ matrix.arch }}-buildx-${{ github.event.inputs.pipeline_name }}-

- name: Log in to Docker Hub
uses: docker/login-action@v2
with:
username: ${{ env.DOCKER_USERNAME }}
password: ${{ env.DOCKER_PASSWORD }}

- name: Build image for ${{ matrix.arch }}
run: |
docker buildx build \
--platform ${{ matrix.platform }} \
--build-arg WORK_DIR=${{ needs.resolve-config.outputs.work_dir }} \
--file ${{ needs.resolve-config.outputs.dockerfile }} \
--tag egovio/${{ needs.resolve-config.outputs.image_name }}:${{ needs.resolve-config.outputs.tag }}-${{ matrix.arch }} \
--cache-from=type=local,src=/tmp/.buildx-cache \
--cache-to=type=local,dest=/tmp/.buildx-cache,mode=max \
--push \
--iidfile digest.txt \
.

- name: Inspect Manifest List
run: |
docker buildx imagetools inspect egovio/${{ needs.resolve-config.outputs.image_name }}:${{ needs.resolve-config.outputs.tag }}-${{ matrix.arch }}

- name: Export Digest (amd64)
if: matrix.arch == 'amd64'
id: digest_amd64
run: |
digest=$(docker buildx imagetools inspect \
egovio/${{ needs.resolve-config.outputs.image_name }}:${{ needs.resolve-config.outputs.tag }}-${{ matrix.arch }} \
--format '{{json .}}' | jq -r '.manifest.manifests[] | select(.platform.architecture=="amd64" and .platform.os=="linux") | .digest')
echo "digest=$digest" >> $GITHUB_OUTPUT

- name: Export Digest (arm64)
if: matrix.arch == 'arm64'
id: digest_arm64
run: |
digest=$(docker buildx imagetools inspect \
egovio/${{ needs.resolve-config.outputs.image_name }}:${{ needs.resolve-config.outputs.tag }}-${{ matrix.arch }} \
--format '{{json .}}' | jq -r '.manifest.manifests[] | select(.platform.architecture=="arm64" and .platform.os=="linux") | .digest')
echo "digest=$digest" >> $GITHUB_OUTPUT

create-manifest:
Comment on lines +134 to +205

Check warning

Code scanning / CodeQL

Workflow does not contain permissions Medium

Actions job or workflow does not limit the permissions of the GITHUB_TOKEN. Consider setting an explicit permissions block, using the following as a minimal starting point: {contents: read}

Copilot Autofix

AI about 1 month ago

To fix the problem, we should set an explicit permissions block for the relevant job or workflow. This ensures that the GITHUB_TOKEN only has the minimal permissions needed during run, reducing repository risk. Since the build-matrix job does not interact with the repository except possibly to read its contents (for actions/checkout), the least privilege starting point is contents: read. The permissions block may be added at the workflow root (affecting all jobs), or at the job level for build-matrix. To minimize surprise, add it only to build-matrix as CodeQL highlighted that job.
The edit is:

  • Within the build-matrix job (underneath 134: name: Build application ${{ matrix.arch }}), add:
    permissions:
      contents: read

No new methods, imports, or definitions are needed.

Suggested changeset 1
.github/workflows/build.yaml

Autofix patch

Autofix patch
Run the following command in your local git repository to apply this patch
cat << 'EOF' | git apply
diff --git a/.github/workflows/build.yaml b/.github/workflows/build.yaml
--- a/.github/workflows/build.yaml
+++ b/.github/workflows/build.yaml
@@ -132,9 +132,10 @@
 
   build-matrix:
     name: Build application ${{ matrix.arch }}
+    permissions:
+      contents: read
     needs: [resolve-config]
     strategy:
-      matrix:
         include:
           - arch: amd64
             platform: linux/amd64
EOF
@@ -132,9 +132,10 @@

build-matrix:
name: Build application ${{ matrix.arch }}
permissions:
contents: read
needs: [resolve-config]
strategy:
matrix:
include:
- arch: amd64
platform: linux/amd64
Copilot is powered by AI and may make mistakes. Always verify output.
name: Create and Push Manifest
needs: [build-matrix, resolve-config]
runs-on: ubuntu-latest
steps:
- name: Log in to Docker Hub
uses: docker/login-action@v2
with:
username: ${{ env.DOCKER_USERNAME }}
password: ${{ env.DOCKER_PASSWORD }}

- name: Create and push manifest
run: |
docker manifest create egovio/${{ needs.resolve-config.outputs.image_name }}:${{ needs.resolve-config.outputs.tag }} \
--amend egovio/${{ needs.resolve-config.outputs.image_name }}@${{ needs.build-matrix.outputs.amd64_digest }} \
--amend egovio/${{ needs.resolve-config.outputs.image_name }}@${{ needs.build-matrix.outputs.arm64_digest }}
docker manifest push egovio/${{ needs.resolve-config.outputs.image_name }}:${{ needs.resolve-config.outputs.tag }}

- name: Cleanup local manifest refs
run: |
docker manifest rm egovio/${{ needs.resolve-config.outputs.image_name }}:${{ needs.resolve-config.outputs.tag }}-amd64 || true
docker manifest rm egovio/${{ needs.resolve-config.outputs.image_name }}:${{ needs.resolve-config.outputs.tag }}-arm64 || true

- name: Add summary to GitHub Actions
run: |
echo "- Image: egovio/${{ needs.resolve-config.outputs.image_name }}:${{ needs.resolve-config.outputs.tag }}" >> $GITHUB_STEP_SUMMARY
echo "- Platform: amd64, arm64" >> $GITHUB_STEP_SUMMARY
Comment on lines +206 to +231

Check warning

Code scanning / CodeQL

Workflow does not contain permissions Medium

Actions job or workflow does not limit the permissions of the GITHUB_TOKEN. Consider setting an explicit permissions block, using the following as a minimal starting point: {}

Copilot Autofix

AI about 1 month ago

To mitigate the risk, an explicit permissions block must be added. The best practice is to set permissions at the top (root) of the workflow so that it automatically applies to all jobs. This should specify only the minimum required permissions. For most build-and-push Docker workflows that do not interact with the GitHub API to write to the repository, read-only access to repository contents is typically sufficient: permissions: { contents: read }. If a job later needs an elevated permission (e.g., to create a release, update a PR, etc.), it can be specified in that job only.

Steps:

  • Insert a permissions block at the root of the workflow (immediately after name: ... and run-name: ..., and before on:).
  • Set to contents: read for the minimum safe starting permissions.
  • No additional imports, methods, or variable definitions are needed.

Suggested changeset 1
.github/workflows/build.yaml

Autofix patch

Autofix patch
Run the following command in your local git repository to apply this patch
cat << 'EOF' | git apply
diff --git a/.github/workflows/build.yaml b/.github/workflows/build.yaml
--- a/.github/workflows/build.yaml
+++ b/.github/workflows/build.yaml
@@ -1,5 +1,7 @@
 name: Build Pipeline
 run-name: Build ${{ github.event.inputs.pipeline_name }}
+permissions:
+  contents: read
 
 on:
   workflow_dispatch:
EOF
@@ -1,5 +1,7 @@
name: Build Pipeline
run-name: Build ${{ github.event.inputs.pipeline_name }}
permissions:
contents: read

on:
workflow_dispatch:
Copilot is powered by AI and may make mistakes. Always verify output.
2 changes: 1 addition & 1 deletion .gitignore
Original file line number Diff line number Diff line change
Expand Up @@ -2,4 +2,4 @@
accelerators/frontend/micro-ui-internals/node_modules/*
.idea
index.lock
utilities/
utilities/project-factory/
Loading
Loading