Skip to content

chore: fix Ci/guard send tweet #529

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

chore: fix Ci/guard send tweet #529

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
cd62915
docs: improve CONTRIBUTING.md formatting and clarity
theorjiugovictor Nov 6, 2025
a9cc13d
ci: guard send-tweet workflow for forks and missing secrets\n\n- Run …
theorjiugovictor Nov 6, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 8 additions & 2 deletions .github/workflows/send-tweet.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,10 +1,16 @@
name: Send a Tweet
on: [push]
on:
push:
branches:
- main
jobs:
tweet:
# Only run in the upstream repo; secrets guard applied at step level
if: github.repository == 'MichaelCade/90DaysOfDevOps'
runs-on: ubuntu-latest
steps:
- uses: ethomson/send-tweet-action@v1
- name: Send tweet
uses: ethomson/send-tweet-action@v1
with:
status: "👋 Hey Everyone!. This is an automated message 🤖 to let you know that there has been an update on the #90DaysOfDevOps repository, Commit message (${{ github.event.head_commit.message }}) You can check it out https://github.com/MichaelCade/90DaysOfDevOps"
consumer-key: ${{ secrets.TWITTER_CONSUMER_API_KEY }}
Expand Down
12 changes: 6 additions & 6 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,10 +33,10 @@ To send us a pull request, please:
1. Fork the repository.
2. Modify the source; please focus on the **specific** change you are contributing.
3. Ensure local tests pass.
4. Updated the documentation, if required.
4. Commit to your fork [using a clear commit messages](http://chris.beams.io/posts/git-commit/). We ask you to please use [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/).
5. Send us a pull request, answering any default questions in the pull request.
6. Pay attention to any automated failures reported in the pull request, and stay involved in the conversation.
4. Update the documentation, if required.
5. Commit to your fork [using clear commit messages](http://chris.beams.io/posts/git-commit/). We ask you to please use [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/).
6. Send us a pull request, answering any default questions in the pull request.
7. Pay attention to any automated failures reported in the pull request, and stay involved in the conversation.

GitHub provides additional document on [forking a repository](https://help.github.com/articles/fork-a-repo/) and
[creating a pull request](https://help.github.com/articles/creating-a-pull-request/).
Expand All @@ -54,15 +54,15 @@ This is a rough outline of what a contributor's workflow looks like:
Example:

``` shell
git remote add upstream https://github.com/vmware-samples/packer-examples-for-vsphere.git
git remote add upstream https://github.com/MichaelCade/90DaysOfDevOps.git
git checkout -b my-new-feature main
git commit -s -a
git push origin my-new-feature
```

### Staying In Sync With Upstream

When your branch gets out of sync with the 90DaysOfDevOps/main branch, use the following to update:
When your branch gets out of sync with the `90DaysOfDevOps/main` branch, use the following to update:

``` shell
git checkout my-new-feature
Expand Down