Skip to content

Commit 1dfe2aa

Browse files
committed
Renames solution in README files.
Updates README files to reflect the solution's rename, ensuring accurate naming and branding across the documentation. This change aligns the README with the new project name.
1 parent bcf7d48 commit 1dfe2aa

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

README.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
1-
# ExtensibleMessageBroker
1+
# ExtensibleDataPipeline
22

3-
[![release](https://github.com/magicxor/ExtensibleMessageBroker/actions/workflows/release.yml/badge.svg)](https://github.com/magicxor/ExtensibleMessageBroker/actions/workflows/release.yml)
4-
[![Ask DeepWiki](https://deepwiki.com/badge.svg)](https://deepwiki.com/magicxor/ExtensibleMessageBroker)
3+
[![release](https://github.com/magicxor/ExtensibleDataPipeline/actions/workflows/release.yml/badge.svg)](https://github.com/magicxor/ExtensibleDataPipeline/actions/workflows/release.yml)
4+
[![Ask DeepWiki](https://deepwiki.com/badge.svg)](https://deepwiki.com/magicxor/ExtensibleDataPipeline)
55

6-
ExtensibleMessageBroker pulls data from one place (a data source) and pushes it to another places (targets).
6+
ExtensibleDataPipeline pulls data from one place (a data source) and pushes it to another places (targets).
77

88
![Imgur](https://i.imgur.com/yJM83Th.png)
99

10-
You can create as many data source providers and target providers as you want. ExtensibleMessageBroker will import them via **Managed Extensibility Framework**.
10+
You can create as many data source providers and target providers as you want. ExtensibleDataPipeline will import them via **Managed Extensibility Framework**.

0 commit comments

Comments
 (0)