Skip to content

Commit 15151ee

Browse files
committed
feat(button): squash for file tracking
1 parent f64be70 commit 15151ee

File tree

120 files changed

+11754
-14329
lines changed

Some content is hidden

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

120 files changed

+11754
-14329
lines changed

.commitlintrc.json

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,7 @@
2525
"security",
2626
"config"
2727
]
28-
]
28+
],
29+
"header-max-length": [ 2, "always", 100 ]
2930
}
3031
}

.config/dotnet-tools.json

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
{
2+
"version": 1,
3+
"isRoot": true,
4+
"tools": {
5+
"dotnet-reportgenerator-globaltool": {
6+
"version": "5.4.7",
7+
"commands": [
8+
"reportgenerator"
9+
],
10+
"rollForward": false
11+
}
12+
}
13+
}

.github/PULL_REQUEST_TEMPLATE.md

Lines changed: 48 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,48 @@
1+
# PR Template
2+
3+
## TODO:
4+
Test it here too
5+
https://technologyenhancedlearning.github.io/GitPageBlazorWASM-TestGHPage/
6+
check version matches branch name and pullrequest release
7+
- maybe a rule that any introduced css for example if bringing in an enum. needs to be refactored to nhse-tel? so tel-nhse is source of truth on all things css
8+
9+
10+
## TODO: About
11+
- SO FAR no js controllers are not going to be covered in testing in the package it will be done by how used in LH
12+
But in future we could simulate them with just an api with stock response or find a programatic way, or build a hosted environment.
13+
The gh-page are pure wasm so not supported for nojs
14+
15+
- brave check no js (Locally not on wasm static test page)
16+
17+
## TODO: This is just replicating LH for now ... ideas
18+
- Link to replicated component
19+
- Link design confluence if coming from design
20+
- Tick box for JS
21+
- If testers find an issue create an automated test of what they did, even potentially with playright record test functionality
22+
- something about is there a linked lh branch using the change
23+
24+
### JIRA link
25+
[TD-####](https://hee-tis.atlassian.net/browse/TD-####)
26+
27+
### Description
28+
_Describe what has changed and how that will affect the app. If relevant, add links to any sources/documentation you used. Highlight anything unusual and give people context around particular decisions._
29+
30+
### Screenshots
31+
_Paste screenshots for all views created or changed: mobile, tablet and desktop, wave analyser showing no errors._
32+
33+
-----
34+
### Developer checks
35+
(Leave tasks unticked if they haven't been appropriate for your ticket.)
36+
37+
I have:
38+
- [ ] Run the IDE auto formatter on all files I’ve worked on and made sure there are no IDE errors relating to them
39+
- [ ] Written or updated tests for the changes (accessibility ui tests for views, tests for controller, data services, services, view models created or modified) and made sure all tests are passing
40+
- [ ] Manually tested my work with and without JavaScript (adding notes where functionality requires JavaScript)
41+
- [ ] Tested any Views or partials created or changed with [Wave Chrome plugin](https://chrome.google.com/webstore/detail/wave-evaluation-tool/jbbplnpkjmmeebjpijfedlgcdilocofh/related). Addressed any valid accessibility issues and documented any invalid errors
42+
- [ ] Updated my Jira ticket with testing notes, including information about other parts of the system that were touched as part of the MR and need to be tested to ensure nothing is broken
43+
- [ ] Scanned over my pull request in GitHub and addressed any warnings from the GitHub Build and Test checks in the GitHub PR ‘Files Changed’ tab
44+
Either:
45+
- [ ] Documented my work in [Confluence](https://hee-tis.atlassian.net/wiki/spaces/TP/pages/3461087233/Development), updating any business rules applied or modified. Updated GitHub readme/documentation for the repository if appropriate. List of documentation links added/changed:
46+
- [doc_1_here](link_1_here)
47+
Or:
48+
- [ ] Confirmed that none of the work that I have undertaken requires any updates to documentation

.github/dependabot.yml

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
version: 2
2+
updates:
3+
- package-ecosystem: "nuget"
4+
directory: "/"
5+
schedule:
6+
interval: "daily"
7+
open-pull-requests-limit: 100
8+
target-branch: "Automatic_version_update_dependabot"
9+
10+
- package-ecosystem: "npm"
11+
directory: "/"
12+
schedule:
13+
interval: "daily"
14+
open-pull-requests-limit: 100
15+
target-branch: "Automatic_version_update_dependabot"
16+
17+
Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
# The intention is minor and patch should be merged into the dependabot branch automatically
2+
3+
name: Dependabot Auto-Merge
4+
5+
on:
6+
pull_request:
7+
branches: [ Automatic_version_update_dependabot ]
8+
9+
permissions:
10+
contents: write
11+
pull-requests: write
12+
13+
jobs:
14+
# works alongside branch protection rules
15+
auto-merge-minor-and-patch:
16+
runs-on: ubuntu-latest
17+
if: ${{ github.actor == 'dependabot[bot]' }}
18+
steps:
19+
- name: Extract update type
20+
id: extract
21+
run: |
22+
PR_TITLE="${{ github.event.pull_request.title }}"
23+
if [[ $PR_TITLE == *"(major)"* ]]; then
24+
echo "update_type=major" >> $GITHUB_OUTPUT
25+
else
26+
echo "update_type=minor_or_patch" >> $GITHUB_OUTPUT
27+
fi
28+
29+
- name: Set up GitHub CLI
30+
uses: cli/cli-action@v2
31+
32+
- name: Auto-merge non-major updates
33+
if: ${{ steps.extract.outputs.update_type == 'minor_or_patch' }}
34+
run: gh pr merge --auto --merge "$PR_URL"
35+
env:
36+
PR_URL: ${{ github.event.pull_request.html_url }}
37+
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

0 commit comments

Comments
 (0)