Skip to content

Commit 764a443

Browse files
committed
fix typo & try to fix codecov upload
1 parent 4ad97a0 commit 764a443

2 files changed

Lines changed: 3 additions & 2 deletions

File tree

.github/workflows/ci.yml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -40,3 +40,4 @@ jobs:
4040
- uses: codecov/codecov-action@v5
4141
with:
4242
files: lcov.info
43+
token: ${{ secrets.CODECOV_TOKEN }}

docs/src/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -130,7 +130,7 @@ Since the theory behind SymmetricTightBinding.jl is anchored in symmetry analysi
130130

131131
For instance, we can label the previously constructed band structure with the little group irrep labels at high-symmetry **k**-points:
132132
```@example basic-use
133-
plot(kpi, Es; annotations=collect_irrep_annotations(ptbm))
133+
plot(kpi, Es; annotations = collect_irrep_annotations(ptbm))
134134
```
135135

136136
Similarly, we can analyze the compatibility respecting bands contained in `ptbm` via [`collect_compatible`](@ref). Here, since we our model contains only a single band representation - and one which is intrinsically connected - such an analysis has only possible answer (the connected band representation itself):
@@ -144,7 +144,7 @@ We can easily set up a more interesting situation, however, by incorporating mor
144144
cbr′ = @composite brs[5] + brs[1]
145145
tbm′ = tb_hamiltonian(cbr′)
146146
ptbm′ = tbm′([-4, -0, -0.1, 0.0, 1.0, -1.0, 1.0])
147-
plot(kpi, spectrum(ptbm′, kpi); annotations=irrep_annotations(ptbm))
147+
plot(kpi, spectrum(ptbm′, kpi); annotations = collect_irrep_annotations(ptbm))
148148
```
149149
The band structures features two connected groups of bands. We can obtain the same result (via a compatibility-analysis involving only the high-symmetry **k**-points) via `collect_compatible`:
150150
```@example basic-use

0 commit comments

Comments
 (0)