-
Notifications
You must be signed in to change notification settings - Fork 554
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
[EN] update Tightly Coupled Architecture #2658
[EN] update Tightly Coupled Architecture #2658
Conversation
✅ Deploy Preview for cncfglossary ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @Garima-Negi
Thanks! LGTM.
(please resolve the merge conflict)
to resolve merge conflict, I'm getting this message in the PR UI : |
Hi @Garima-Negi :) Could you resolve the conflict by your local branch? If you feel difficult on that, you may open a new PR since the suggested change is simple. |
hei @Garima-Negi, are you able to do it? Or do you need some support? |
Signed-off-by: Garima Negi <garima.negy@gmail.com>
d1311a3
to
f9d47d4
Compare
I've rebased the commit on |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the update @Garima-Negi, and for your patience while we reviewed it.
Describe your changes
This PR fixes the filename and the page title for tightly coupled architecture.
This matches Title in 'loosely coupled architecture'
Related issue number or link (ex:
resolves #issue-number
)Checklist before opening this PR (put
x
in the checkboxes)git commit -s
) is to affirm that commits comply DCO. If you are working locally, you could add an alias to yourgitconfig
by runninggit config --global alias.ci "commit -s"
.