Skip to content

Commit

Permalink
Automated deployment to update events 2021-08-22 (#371)
Browse files Browse the repository at this point in the history
Co-authored-by: github-actions <github-actions@users.noreply.github.com>
  • Loading branch information
github-actions[bot] and github-actions committed Aug 22, 2021
1 parent 8448a35 commit d691d89
Show file tree
Hide file tree
Showing 4 changed files with 60 additions and 0 deletions.
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
---
event_type: PullRequestReviewCommentEvent
avatar: "https://avatars.githubusercontent.com/u/814322?"
user: vsoch
date: 2021-08-21
repo_name: con/tributors
html_url: https://github.com/con/tributors/pull/61#discussion_r693382897
repo_url: https://github.com/con/tributors
---

<a href='https://github.com/vsoch' target='_blank'>vsoch</a> <a href='https://github.com/con/tributors/pull/61#discussion_r693382897' target='_blank'>commented</a> on <a href='https://github.com/con/tributors' target='_blank'>con/tributors</a>

<a href='https://github.com/con/tributors/pull/61#discussion_r693382897' target='_blank'>View Comment</a>
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
---
event_type: IssuesEvent
avatar: "https://avatars.githubusercontent.com/u/814322?"
user: vsoch
date: 2021-08-21
repo_name: hpcng/singularity-userdocs
html_url: https://github.com/hpcng/singularity-userdocs/issues/408
repo_url: https://github.com/hpcng/singularity-userdocs
---

<a href='https://github.com/vsoch' target='_blank'>vsoch</a> open issue <a href='https://github.com/hpcng/singularity-userdocs/issues/408' target='_blank'>hpcng/singularity-userdocs#408</a>.

<p>Ensure that previous singularity.lbl.gov docs are reproduced</p><small>I've recently been going through old Google Groups and GitHub issues, and there is a surprising number of references to old tutorials, instructions, or content on the singularity.lbl.gov page. Currently, if the user clicks they are taken to the home of the hpcng user docs, which gives them no idea about the previous content, is confusing, and considered bad practice to have so many broken links. I've discussed this in slack, and there are a few options:...</small><a href='https://github.com/hpcng/singularity-userdocs/issues/408' target='_blank'>View Comment</a>
Expand Down
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
---
event_type: PushEvent
avatar: "https://avatars.githubusercontent.com/u/814322?"
user: vsoch
date: 2021-08-21
repo_name: vsoch/opensource-heartbeat
html_url: https://github.com/vsoch/opensource-heartbeat/commit/8448a35f41f5c121b13585dc057daf6ed4877d1d
repo_url: https://github.com/vsoch/opensource-heartbeat
---

<a href='https://github.com/vsoch' target='_blank'>vsoch</a> pushed to <a href='https://github.com/vsoch/opensource-heartbeat' target='_blank'>vsoch/opensource-heartbeat</a>

<small>Automated deployment to update events 2021-08-21 (#370)

Co-authored-by: github-actions <github-actions@users.noreply.github.com></small>

<a href='https://github.com/vsoch/opensource-heartbeat/commit/8448a35f41f5c121b13585dc057daf6ed4877d1d' target='_blank'>View Commit</a>
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
---
event_type: PushEvent
avatar: "https://avatars.githubusercontent.com/u/814322?"
user: vsoch
date: 2021-08-22
repo_name: vsoch/chonker-awards
html_url: https://github.com/vsoch/chonker-awards/commit/d8566a4f8bdde6e11fa2d9e6e42d013c240f8cc8
repo_url: https://github.com/vsoch/chonker-awards
---

<a href='https://github.com/vsoch' target='_blank'>vsoch</a> pushed to <a href='https://github.com/vsoch/chonker-awards' target='_blank'>vsoch/chonker-awards</a>

<small>Merge pull request #203 from vsoch/chonkers/update-2021-08-22

[chonkers] chonkers/update-2021-08-22</small>

<a href='https://github.com/vsoch/chonker-awards/commit/d8566a4f8bdde6e11fa2d9e6e42d013c240f8cc8' target='_blank'>View Commit</a>

0 comments on commit d691d89

Please sign in to comment.