Questions / Answers from ops members

ExperimentsInHonesty commented 1 year ago

Dependency

When there is a question to be answered

Overview

If you have questions, put them in this issue so that we can answer them and keep the info around permanently (adding it to wiki, etc.)

Action Items

[ ] Add your question to a comment
[ ] if you have the answer to someone else's questions, add a comment, and quote their question in your comment using the > character to create a blockquote. Indicate if you think the question and answer should be added to the wiki
[ ] add the label ready for CoP lead
[ ] move to the question's column.

Resources/Instructions

[ ] https://github.com/hackforla/ops/wiki

drakeredwind01 commented 3 months ago

R.E.

[ ] Create a new branch from main by executing the command

git checkout -b issue-number-add-new-iam-user

my issue number is #36 would an example be

git checkout -b 36-add-new-iam-user
or
git checkout -b 36-drakeredwind01
git checkout -b 36-add-new-drakeredwind01
git checkout -b 36-add-new-iam-user-drakeredwind01

chelseybeck commented 3 months ago

@drakeredwind01 the last one would be best

drakeredwind01 commented 3 months ago

This has been answered, see https://github.com/hackforla/ops/issues/93#issuecomment-2418307622

Q: should we properly categorize our branches?

my mentor says it might be a good idea to incorporate common practice branch grouping

bugfix/no_destination_for_href
feature/adding_picture_of_a_cute_puppy
release/cute_puppy_update_for_better_retention
hotfix/corrupt_image_breaks_the_site_fix

for example:

git checkout -b feature/36-add-new-iam-user-drakeredwind01
instead of
git checkout -b 36-add-new-iam-user-drakeredwind01

doing this would make finding specific branches much easier as each prefaced catagory would show as another folder with all concerning branches within.

HFLA
├───bugfix
│   ├───css_is_broken_on_home_page
│   └───no_destination_for_href
├───feature
│   └───adding_picture_of_a_cute_puppy
├───release
│   └───cute_puppy_update_for_better_retention
├───hotfix
│   └───corrupt_image_breaks_the_site_fix
├───iam_users
│   └───every_thing_is_on_on_fire_help
└───admin
    └───sigh

can also add features such as admin, iam_users, etc. this is a standard used in most places in accordance with atlassian.com

branch	how to incorperate	notes
bugfix:	[bugfix/]	problem that should be fixed that doesn't add any new functionality
Feature	[feature/]	an attribute or characteristic that adds value to the product.
Release	[release/]	where the maintainers believe the software is worth trying and using
Hotfix	[hotfix/]	should never use. needs to be added right away into production

drakeredwind01 commented 3 months ago

Hi, how have you been doing? i'm having trouble starting from the part of:

[x] Execute the command terraform init to initialize terraform in the directory. Address any failures that arise (if any).

would you mind guiding me through this challenging part? i'm using windows and pycharm it's fastest to contact me here https://discord.gg/WbcWqVq please use '@drakeredwind01' to notify me

ale210 commented 1 month ago

Q: https://github.com/hackforla/ops/issues/93#issuecomment-2290526449 should we properly categorize our branches?

Question Details

Q: should we properly categorize our branches? my mentor says it might be a good idea to incorporate common practice branch grouping ```bash bugfix/no_destination_for_href feature/adding_picture_of_a_cute_puppy release/cute_puppy_update_for_better_retention hotfix/corrupt_image_breaks_the_site_fix ``` for example: ```bash git checkout -b feature/36-add-new-iam-user-drakeredwind01 instead of git checkout -b 36-add-new-iam-user-drakeredwind01 ``` doing this would make finding specific branches much easier as each prefaced catagory would show as another folder with all concerning branches within. ```bash HFLA ├───bugfix │ ├───css_is_broken_on_home_page │ └───no_destination_for_href ├───feature │ └───adding_picture_of_a_cute_puppy ├───release │ └───cute_puppy_update_for_better_retention ├───hotfix │ └───corrupt_image_breaks_the_site_fix ├───iam_users │ └───every_thing_is_on_on_fire_help └───admin └───sigh ``` can also add features such as admin, iam_users, etc. this is a standard used in most places in accordance with [atlassian.com](https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow) | branch | how to incorperate | notes | |---------|--------------------|----------------------------------------------------------------------| | bugfix: | [bugfix/] | problem that should be fixed that doesn't add any new functionality | | Feature | [feature/] | an attribute or characteristic that adds value to the product. | | Release | [release/] | where the maintainers believe the software is worth trying and using | | Hotfix | [hotfix/] | should never use. needs to be added right away into production |

A: So our infra repo is a bit different - because it's an infrastructure repo and not a development repo, we don't have things like feature branches, hotfixes, etc. Our workflow is pretty simple, where the prefix for branch names are the issue number and description

hackforla / ops