99 Commits

Author SHA1 Message Date
Blog Creator
f1dc3e511e 'Ban ineffective, parents know best.' 2025-06-23 04:21:00 +00:00
Blog Creator
7443c82e88 'Fix: Analyze failing social media ban' 2025-06-22 03:47:31 +00:00
Blog Creator
176e6caeb5 'Ban ineffective, parental controls work better.' 2025-06-20 03:47:45 +00:00
307146b763 typo 2025-06-20 11:43:42 +10:00
ab8ad6ffae Human edits to the AI draft 2025-06-20 11:42:40 +10:00
Blog Creator
2cda84da5e 'Fix: Ban flawed, focus on education' 2025-06-20 01:17:04 +00:00
2905c2917f Update src/content/when_to_use_ai.md
All checks were successful
Build and Push Image / Build and push image (push) Successful in 18m18s
2025-06-06 13:33:36 +10:00
ec0798dff2 Update for clarity of the AI response
Some checks failed
Build and Push Image / Build and push image (push) Has been cancelled
2025-06-06 13:32:19 +10:00
f41dbc802e Merge pull request 'when_to_use_ai' (#12) from when_to_use_ai into master
All checks were successful
Build and Push Image / Build and push image (push) Successful in 11m27s
Reviewed-on: #12
2025-06-06 12:31:58 +10:00
e7f996306f Human edit and update 2025-06-06 12:30:42 +10:00
Blog Creator
22c521293f 'Clarify AI usage scenarios effectively.' 2025-06-06 02:28:07 +00:00
Blog Creator
74f8c8607b 'Add clarity on AI limitations.' 2025-06-06 01:57:04 +00:00
8c342d994e fix conflicts 2025-06-06 11:32:25 +10:00
Blog Creator
bcc41ed4c3 '```
git commit -m "AI: Know when to use it"
```

**Explanation of the commit message:**

*   **Concise:** It's short and to the point, adhering to the common 5-word limit.
*   **Descriptive:** It accurately reflects the content of the blog post – a discussion about when to utilize AI.
*   **Action-oriented:**  Implies a need for thoughtful consideration.
'
2025-06-06 11:30:38 +10:00
Blog Creator
fc48d9a4fd '```
feat: Add blog post on AI usage scenarios
```'
2025-06-06 11:30:03 +10:00
Blog Creator
191805461d '```
feat: Add blog post on AI usage scenarios
```'
2025-06-06 11:29:09 +10:00
Blog Creator
c2142f7f63 '```
git commit -m "AI: Know when to use it"
```

**Explanation of the commit message:**

*   **Concise:** It's short and to the point, adhering to the common 5-word limit.
*   **Descriptive:** It accurately reflects the content of the blog post – a discussion about when to utilize AI.
*   **Action-oriented:**  Implies a need for thoughtful consideration.
'
2025-06-06 11:28:17 +10:00
Blog Creator
9c92d19943 '```
feat: Add blog post on AI usage scenarios
```'
2025-06-06 11:27:23 +10:00
aead9151c0 Update src/content/when_to_use_ai.md 2025-06-06 11:26:13 +10:00
14636a4d3b update so pelican can use - must remember 2025-06-06 11:26:12 +10:00
d6d6f1893e stray w 2025-06-06 11:25:43 +10:00
abf6f3feda fix push settings 2025-06-06 11:25:43 +10:00
7a4d06bbef cleanup of kube stuff 2025-06-06 11:25:43 +10:00
efad73a1a4 wrap the password 2025-06-06 11:25:43 +10:00
50af2eccb3 kube pipeline manual step and kubectl yaml 2025-06-06 11:25:43 +10:00
e9a7daf5b3 Change workflow push to master only 2025-06-06 11:25:43 +10:00
eac2f648c0 Update src/content/when_to_use_ai.md
All checks were successful
Build and Push Image / Build and push image (push) Successful in 7m30s
2025-06-06 10:29:51 +10:00
79d53d3462 update so pelican can use - must remember
All checks were successful
Build and Push Image / Build and push image (push) Successful in 7m23s
2025-06-06 10:17:13 +10:00
6dd6e92d93 Merge pull request 'stray -' (#11) from kube_deployment into master
All checks were successful
Build and Push Image / Build and push image (push) Successful in 7m41s
Reviewed-on: #11
2025-06-06 10:00:37 +10:00
3db9f63246 stray w 2025-06-06 09:59:47 +10:00
6552ba503b Merge pull request 'fix push settings' (#10) from kube_deployment into master
Some checks failed
Build and Push Image / Build and push image (push) Failing after 6m1s
Reviewed-on: #10
2025-06-06 09:53:14 +10:00
202c787f19 fix push settings 2025-06-06 09:52:38 +10:00
61324ff499 Merge pull request 'kube_deployment' (#9) from kube_deployment into master
Some checks failed
Build and Push Image / Build and push image (push) Failing after 9m24s
Reviewed-on: #9
2025-06-06 09:32:18 +10:00
859c40c55c cleanup of kube stuff 2025-06-06 09:31:43 +10:00
92dd043b35 wrap the password 2025-06-06 09:29:24 +10:00
761265a467 kube pipeline manual step and kubectl yaml 2025-06-06 09:25:31 +10:00
da1bfd4779 Change workflow push to master only
All checks were successful
Build and Push Image / Build and push image (push) Successful in 10m7s
2025-06-04 20:10:41 +10:00
Blog Creator
1f4b7100bc '```
All checks were successful
Build and Push Image / Build and push image (push) Has been skipped
git commit -m "AI: Know when to use it"
```

**Explanation of the commit message:**

*   **Concise:** It's short and to the point, adhering to the common 5-word limit.
*   **Descriptive:** It accurately reflects the content of the blog post – a discussion about when to utilize AI.
*   **Action-oriented:**  Implies a need for thoughtful consideration.
'
2025-05-30 07:43:58 +00:00
Blog Creator
3ed8f91303 '```
All checks were successful
Build and Push Image / Build and push image (push) Has been skipped
feat: Add blog post on AI usage scenarios
```'
2025-05-30 07:18:43 +00:00
49167ee308 Merge pull request 'when_to_use_ai' (#8) from when_to_use_ai into master
All checks were successful
Build and Push Image / Build and push image (push) Successful in 5m59s
Reviewed-on: #8
2025-05-30 16:28:20 +10:00
b9210910f5 Had to make a new one and this looked better
All checks were successful
Build and Push Image / Build and push image (push) Has been skipped
2025-05-30 16:27:36 +10:00
Blog Creator
040d90ce73 '```git
All checks were successful
Build and Push Image / Build and push image (push) Has been skipped
git commit -m "AI: Know when to apply it"
```

**Explanation of the commit message:**

*   **Concise:** It's short and to the point, fitting within the recommended 50-character limit.
*   **Descriptive:** It accurately reflects the content's focus on appropriate AI usage.
*   **Action-oriented:**  "Know when to apply it" suggests a key takeaway for the reader.
'
2025-05-30 06:20:58 +00:00
70c1dfdbb2 Merge pull request 'when_to_use_ai' (#7) from when_to_use_ai into master
All checks were successful
Build and Push Image / Build and push image (push) Successful in 9m32s
Reviewed-on: #7
2025-05-30 15:17:31 +10:00
f5b370e048 update for formatting error
All checks were successful
Build and Push Image / Build and push image (push) Has been skipped
2025-05-30 15:16:26 +10:00
678d7f4308 Added human intro to "when to use ai"
All checks were successful
Build and Push Image / Build and push image (push) Has been skipped
2025-05-30 15:15:35 +10:00
Blog Creator
f3582e5881 '```git
All checks were successful
Build and Push Image / Build and push image (push) Has been skipped
git commit -m "Analyze AI use cases and limitations"
```
'
2025-05-30 05:08:43 +00:00
Blog Creator
74fb66d81e '```
All checks were successful
Build and Push Image / Build and push image (push) Has been skipped
When to use #AI carefully
```'
2025-05-30 04:55:07 +00:00
Blog Creator
874df3c8c3 '```
All checks were successful
Build and Push Image / Build and push image (push) Has been skipped
Add blog post on AI usage scenarios
```'
2025-05-30 04:46:10 +00:00
Blog Creator
2280630149 'Sure, here's your requested 5-word commit message for the blog post:
All checks were successful
Build and Push Image / Build and push image (push) Has been skipped
"AI vs Traditional: When & Why?"'
2025-05-30 04:30:27 +00:00
Blog Creator
9b440b775a '# Commit Message
All checks were successful
Build and Push Image / Build and push image (push) Has been skipped
When to use AI: Structured Tasks vs Complex Decisions 🤖🔍📊

<|end_of_solution|>'
2025-05-30 01:03:18 +00:00