Skip to content
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.

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

ci: add discord notification #108

Merged
merged 6 commits into from
Jun 14, 2023

Conversation

Oferlis
Copy link
Contributor

@Oferlis Oferlis commented Jun 10, 2023

Added a discord notification workflow.
The file added was used for testing purposes, and if anyone else would want to test it.
It may also be used to split up the notifying workflow from the other build and publish workflow, and I guess more platform notifications will be added overtime, but it is up to you.

The notification content is:
Screenshot 2023-06-12 at 16 52 05

**when creating the Discord webhook you can choose the name of the bot

@Oferlis Oferlis changed the title Ofer/discord notification feat: add discord notification Jun 11, 2023
first iteration

split file for testing

added step

added link in message

updated message

modified string

update

string
Copy link
Collaborator

@baruchiro baruchiro left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh, I reviewed but I forgot to send my review 😐

.github/workflows/release.yml Outdated Show resolved Hide resolved
.github/workflows/release.yml Outdated Show resolved Hide resolved
@baruchiro baruchiro changed the title feat: add discord notification ci: add discord notification Jun 11, 2023
@baruchiro
Copy link
Collaborator

@Oferlis You can easily get the URL from the action-gh-release, see here.

Copy link
Collaborator

@baruchiro baruchiro left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm blocked from changing the code in this PR, so please apply the two changes I requested and I will merge this.

Thanks!

.github/workflows/notify-release.yml Outdated Show resolved Hide resolved
.github/workflows/release.yml Outdated Show resolved Hide resolved
Oferlis and others added 2 commits June 13, 2023 18:03
added code suggestion

Co-authored-by: Baruch Odem (Rothkoff) <baruchiro@gmail.com>
@baruchiro baruchiro merged commit 249c672 into os-scar:master Jun 14, 2023
5 checks passed
rzarviv pushed a commit to rzarviv/overlay that referenced this pull request Jun 15, 2023
Added a discord notification workflow.
The file added was used for testing purposes, and if anyone else would
want to test it.
It may also be used to split up the notifying workflow from the other
build and publish workflow, and I guess more platform notifications will
be added overtime, but it is up to you.

The notification content is: 
![Screenshot 2023-06-12 at 16 52
05](https://github.com/os-scar/overlay/assets/62609377/1c2b4e94-232a-4eab-8ecb-6e8e49b54fab)


**when creating the Discord webhook you can choose the name of the bot

---------

Co-authored-by: Baruch Odem (Rothkoff) <baruchiro@gmail.com>
rzarviv pushed a commit to rzarviv/overlay that referenced this pull request Jun 15, 2023
organize imports

- changed "chrome" to "browser"  in background-events.js

- added "tabs" permission to firefox manifest
- moved event handler of URL_CHANGED to `content-events.js`
- added a new subscription method for url change in `content.js`

- added a test for issue os-scar#107

- moved EVENT_URL_CHANGED's event handler to the already existing listener.
- changed page locator in test.
- used a MutationObserver to insert `overlay-package-report` after the repository element is rendered (there are cases that the repository selector cannot be found since it's not yet rendered).

- fixed test

lint e2e too

- removed "highlight" and fixed test

- removed `tabs` permission from manifest
- added utility function that waits for element to be rendered
- rewrote test

ci: add discord notification (os-scar#108)

Added a discord notification workflow.
The file added was used for testing purposes, and if anyone else would
want to test it.
It may also be used to split up the notifying workflow from the other
build and publish workflow, and I guess more platform notifications will
be added overtime, but it is up to you.

The notification content is:
![Screenshot 2023-06-12 at 16 52
05](https://github.com/os-scar/overlay/assets/62609377/1c2b4e94-232a-4eab-8ecb-6e8e49b54fab)

**when creating the Discord webhook you can choose the name of the bot

---------

Co-authored-by: Baruch Odem (Rothkoff) <baruchiro@gmail.com>

fix real examples

lint e2e too

- removed "highlight" and fixed test

ci: add discord notification (os-scar#108)

Added a discord notification workflow.
The file added was used for testing purposes, and if anyone else would
want to test it.
It may also be used to split up the notifying workflow from the other
build and publish workflow, and I guess more platform notifications will
be added overtime, but it is up to you.

The notification content is:
![Screenshot 2023-06-12 at 16 52
05](https://github.com/os-scar/overlay/assets/62609377/1c2b4e94-232a-4eab-8ecb-6e8e49b54fab)

**when creating the Discord webhook you can choose the name of the bot

---------

Co-authored-by: Baruch Odem (Rothkoff) <baruchiro@gmail.com>

fix real examples

- fixed typo
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants