This is an automated email from the ASF dual-hosted git repository.
yasith pushed a change to branch feat/svclayer-portal
in repository https://gitbox.apache.org/repos/asf/airavata.git
discard a10b750147 feat(portal): add Next.js frontend application
discard e68d68a194 feat(rest): add REST API controllers, deployment, and
infrastructure
discard dd9da642fa feat(services): add service layer, domain models, and
legacy cleanup
add 2fb23e7b4d refactor: remove legacy modules, Thrift stubs, and dev-tools
add 252297fe44 feat: rewrite domain model, add REST API, and restructure
build
new d7636d2168 feat(portal): add Next.js frontend application
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (a10b750147)
\
N -- N -- N refs/heads/feat/svclayer-portal (d7636d2168)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
