sig-teleirc / infrastructure

#29 Add Fedora Silverblue bridge.
Closed by tjzabel. Opened by tjzabel.
add/silverblue-bot  into  master

Download 29.patch

This PR adds the Fedora Silverblue TG <=> IRC bridge. This is in production.

Metadata Update from @tjzabel:
- Pull-request tagged with: needs testing, type - new bot

1 new commit added

  • fedora_qa => fedora_silverblue cn

LGTM. I did not read the encrypted data, but since this is not your first rodeo, I am going to assume you got that part right. :)

Merging!

Metadata Update from @jflory7:
- Request assigned

Oh, I refreshed after merging #32. Merge conflict! Because of Ansible Vault, this will need a manual rebase. :persevere:

Metadata Update from @jflory7:
- Pull-request untagged with: needs testing
- Pull-request tagged with: needs changes
- Request assigned

Bridge was finally fixed. For reference, this is what needed to be ran:

/msg ChanServ ACCESS #silverblue ADD tg-*!*@*.rit.edu +V

1 new commit added

  • Add Fedora i3 community.

@jflory7 how exactly does the rebase work with ansible vault? I cannot do a rebase and edit the vault file, as it then is in an invalid format due to merge conflict messages.

3 new commits added

  • Add Fedora i3 community.
  • fedora_qa => fedora_silverblue cn
  • Add Fedora Silverblue bridge.

I manually added the Fedora i3 changes. Is there a better way to do this? I can rollback these commits if so.

Closing and re-pushing PR due to messy git history on this merge.

Pull-Request has been closed by tjzabel
Metadata
tjzabel

needs changes type - new bot

Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.