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
fix BizOps page reference #1670
Comments
@JennMoran you would make those changes in the To clarify, you want to take out the Links? Should Technology Portfolio be represented somewhere else? cc @its-a-lisa |
I think @keithrwilson is taking care of this. @keith can you please confirm? Thanks! |
I was trying to fix it, but I got a little in the weeds with the pull
request while trying to update the other sections. If anyone is able to
help clean up the issues, that would be great.
…On Tue, Nov 26, 2019 at 3:44 PM Jennifer Moran ***@***.***> wrote:
I think @keithrwilson <https://github.com/keithrwilson> is taking care of
this. @keith <https://github.com/keith> can you please confirm? Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1670?email_source=notifications&email_token=AFKFZEO473PEZ5G5HW3M5XLQVWKBVA5CNFSM4JQMO7NKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFHRC5Q#issuecomment-558829942>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFKFZEO5QXHTDNGKJGDWT2TQVWKBVANCNFSM4JQMO7NA>
.
--
*Keith Wilson*
TTS Business Operations
Acting Supervisor, People Ops
U.S. General Services Administration
|
@keithrwilson is this one of the things you're trying to resolve with #1652? I'm happy to help. I think the first thing we should do (as mentioned on that PR) is separate out the content changes from the backend changes. We can do the backend changes with the #1212 issues, and I think doing them both at the same time gets overwhelming. So I propose taking #1652 back to just content changes, and I can get started on #1212 for you. Does that work? |
This issue will be closed as inactive on or after November 23. If we should keep this issue open, please add another comment or remove the |
Closing as stale. Feel free to reopen this issue or create another one if this should still be addressed. |
Originally posted by @JennMoran in #1620 (comment)
The text was updated successfully, but these errors were encountered: