Skip to content

Issues: manekinekko/hexa

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

6 Open 1 Closed
6 Open 1 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Some hexa commands fails if a default resource group is set effort1: hours priority: high scope: azure-cli status: accepted type: bug
#28 opened Aug 23, 2021 by sinedied
1
Az CLI ignores options if environment variables are set effort1: hours priority: high scope: azure-cli status: accepted type: bug
#27 opened Aug 23, 2021 by manekinekko
hexa init and hexa init --just functions --use bazel don't create a project error in ubuntu 20 priority: high scope: hexa status: accepted type: bug
#20 opened May 8, 2020 by cassiolpaixao90
@manekinekko
The .env file is generated with the wrong content communiyt-help Extra attention is needed effort1: hours good first issue Good for newcomers priority: high scope: hexa status: accepted type: bug
#19 opened Feb 13, 2020 by manekinekko
hexa init --just=hosting fails if public folder isn't created communiyt-help Extra attention is needed effort1: hours priority: high scope: hexa type: bug
#18 opened Feb 13, 2020 by manekinekko
Error on hexa init --just=functions effort2: days priority: high scope: hexa status: accepted type: bug
#15 opened Jan 11, 2020 by jackbravo
@manekinekko
14
ProTip! Exclude everything labeled bug with -label:bug.