Skip to content

๐ŸŒŒ CORS์˜ ํŒ€๋ธ”๋กœ๊ทธ์ž…๋‹ˆ๋‹ค. ํšŒ๊ณ ์™€ ๊ฐœ์„ ์„ ์ค‘์‹œํ•˜๋ฉฐ ๊ณ ๋ฏผ์ด ๋‹ด๊ธด ์ฝ”๋“œ๋ฅผ ์ง€ํ–ฅํ•ฉ๋‹ˆ๋‹ค.

License

Notifications You must be signed in to change notification settings

teamcors/teamcors.github.io

Folders and files

NameName
Last commit message
Last commit date

Latest commit

ย 

History

46 Commits
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 

Repository files navigation

profile-large

Conventions

Branch Rules

  • develop/{issue_number}: for blog maintenance
  • docs/{issue_number}: for markdown relatives
  • gh-pages: for deployment

Commit Rules

  • SEMANTIC COMMITS that @Queue-ri told you.
  • All commit messages should contain issue numbers.

Manual Deployment

Before you deploy, you must check if:

  • all edits are merged into main branch
  • you're currently on main branch
  • the deployment commit message contains the lastest SHA of main branch

then launch:

npm run deploy -- -m "chore: Deploy {latest_main_sha}"

About

๐ŸŒŒ CORS์˜ ํŒ€๋ธ”๋กœ๊ทธ์ž…๋‹ˆ๋‹ค. ํšŒ๊ณ ์™€ ๊ฐœ์„ ์„ ์ค‘์‹œํ•˜๋ฉฐ ๊ณ ๋ฏผ์ด ๋‹ด๊ธด ์ฝ”๋“œ๋ฅผ ์ง€ํ–ฅํ•ฉ๋‹ˆ๋‹ค.

Topics

Resources

License

Stars

Watchers

Forks

Contributors 4

  •  
  •  
  •  
  •