ruthwell07/LSFE-Frontend
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
LSFE-Frontend
5 Commits 2 Branches 0 Tags 576 KiB
TypeScript 99%
CSS 0.5%
JavaScript 0.3%
HTML 0.2%
main
Go to file
ruthwell07 4e54edf669
All checks were successful
Build and Deploy LSFE Frontend / build-and-deploy (push) Successful in 4m36s
Details
Merge pull request 'changing of label/brand' (#1) from Maintenance/August2026 into main 
Reviewed-on: #1
2026-08-10 04:17:57 +02:00
.gitea/workflows adding secrete for vite_base_url_api 2026-07-30 14:35:05 +08:00
public for migration to new repo to be able to use the CICD 2026-07-30 13:56:40 +08:00
src changing of label/brand 2026-08-10 10:16:55 +08:00
.eslintrc.json for migration to new repo to be able to use the CICD 2026-07-30 13:56:40 +08:00
.gitignore for migration to new repo to be able to use the CICD 2026-07-30 13:56:40 +08:00
.prettierrc for migration to new repo to be able to use the CICD 2026-07-30 13:56:40 +08:00
eslint.config.js for migration to new repo to be able to use the CICD 2026-07-30 13:56:40 +08:00
index.html for migration to new repo to be able to use the CICD 2026-07-30 13:56:40 +08:00
package-lock.json update the config 2026-07-30 15:57:52 +08:00
package.json update the config 2026-07-30 15:57:52 +08:00
postcss.config.js for migration to new repo to be able to use the CICD 2026-07-30 13:56:40 +08:00
README.md for migration to new repo to be able to use the CICD 2026-07-30 13:56:40 +08:00
tailwind.config.js update the config 2026-07-30 15:57:52 +08:00
tsconfig.app.json for migration to new repo to be able to use the CICD 2026-07-30 13:56:40 +08:00
tsconfig.json for migration to new repo to be able to use the CICD 2026-07-30 13:56:40 +08:00
tsconfig.node.json for migration to new repo to be able to use the CICD 2026-07-30 13:56:40 +08:00
vite.config.ts for migration to new repo to be able to use the CICD 2026-07-30 13:56:40 +08:00

README.md

Introduction

TODO: Give a short introduction of your project. Let this section explain the objectives or the motivation behind this project.

Getting Started

TODO: Guide users through getting your code up and running on their own system. In this section you can talk about:

  1. Installation process
  2. Software dependencies
  3. Latest releases
  4. API references

Build and Test

TODO: Describe and show how to build your code and run the tests.

Contribute

TODO: Explain how other users and developers can contribute to make your code better.

If you want to learn more about creating good readme files then refer the following guidelines. You can also seek inspiration from the below readme files: